On Wed, 7 Nov 2007, J=F6rn Engel wrote:

quoted text
> > The pointer is for communication between the get and kick methods. get(=
)=20
quoted text
> > can  modify kick() behavior by returning a pointer to a data structure =
or=20
quoted text
> > using the pointer to set a flag. F.e. get() may discover that there is =
an=20
quoted text
> > unreclaimable object and set a flag that causes kick to simply undo the=
=20
quoted text
> > refcount increment. get() may build a map for the objects and indicate =
in=20
quoted text
> > the map special treatment.=20
>=20
> Is there a get/kick pair that actually does this?  So far I haven't
> found anything like it.

Hmmm.. Nothing uses it at this point. I went through a series of get/kicks
during development. Some needed it. I suspect that we will need it when we=
=20
implement reallocation instead of simply reclaiming. It is also necessary
if we get into the situation where we want to optimize the reclaim. At=20
that point the kick method needs to know how far get() got before the=20
action was aborted in order to fix up only certain refcounts.

quoted text
> Also, something vaguely matching that paragraph might make sense in a
> kerneldoc header to the function. ;)

Its described in slab.h