Re: [PATCH 02/16] DRBD: lru_cache

[Rik van Riel]

Kyle Moffett wrote:
> On Sun, May 3, 2009 at 8:48 PM, Kyle Moffett <kyle@xxxxxxxxxxxxxxx> wrote:
> > There are a couple trivial tunables you can apply to the model I
> > provided to dramatically change the effect of memory pressure on the
> > LRU:
> >
> > [...]
>
> Ooh, I forgot to mention another biggie:  There's a way to allocate a
> reserve pool of memory (I don't remember the exact API, sorry), which
> can be attached to a specific kmem_cache to be used by processes
> attempting writeout.  This would allow you to allocate more in-use
> elements to make forward progress, even if all of your existing
> elements are already in-use.

Lars,

is using a mempool for allocation, in combination with a
shrinker callback for freeing older entries an option for
DRBD?

It looks like that could get rid of a fair amount of custom infrastructure.

--
All rights reversed.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/