Re: Fixing pool_cache_invalidate(9), final step

[Jean-Yves Migeon <jeanyves.migeon%free.fr@localhost>]

On Mon, 4 Jun 2012 09:10:01 -0500, David Young wrote:
> On Mon, Jun 04, 2012 at 10:34:06AM +0100, Jean-Yves Migeon wrote:
> > [General]
> > - Dumped pool_cache_invalidate_cpu() in favor of pool_cache_xcall()
> > which transfers CPU-bound objects back to the global pool.
> > - Adapt comments accordingly.
>
> pool_cache_xcall() seems to describe how the function works rather 
> than
> what it does.

Yes.

> Is it a new part of the pool_cache(9) API?

No, this function appeared with pool_cache(9). I agree that its name is 
not particularly useful.

> If so, I
> think that the name should say what the function does.

pool_cache_transfer() ?

--
Jean-Yves Migeon
jeanyves.migeon%free.fr@localhost