Lines Matching refs:constructor
106 * user argument passed to the constructor, destructor, and reclaim functions is
209 * the object constructor only when allocating from the slab layer, and only in
217 * on a newly created object (immediately after the constructor).
284 * constructor. While in the magazine it appears allocated from the point of
299 * ... set any initial state not set by the constructor ...
527 * ... set any initial state not set by the constructor ...
1944 * Return -1 if kmem_error, 1 if constructor fails, 0 if successful.
2470 * Must advance curr pointer before calling a constructor that
2475 /* run constructor */
2480 printf("name='%s' cache=0x%p: kmem cache constructor failed\n",
2487 /* fall back to normal alloc if the constructor fails */
2616 * so get a raw buffer from the slab layer and apply its constructor.
2625 * Make kmem_cache_alloc_debug() apply the constructor for us.
2634 * here because the constructor failed (indicated by a
3734 * That is, the constructor (if any) must leave the object in a valid state for
3742 int (*constructor)(void *, void *, int), /* object constructor */
3873 cp->cache_constructor = constructor;
3954 * there is a constructor avoids some tricky issues with debug setup
4170 * enforce this by setting land mines in the constructor, destructor,
4893 * Make kmem_cache_alloc_debug() apply the constructor for us.