lkml.org 
[lkml]   [2009]   [May]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 02/16] DRBD: lru_cache
On Mon, May 04, 2009 at 12:12:07PM -0400, Rik van Riel wrote:
> Kyle Moffett wrote:
>> On Sun, May 3, 2009 at 8:48 PM, Kyle Moffett <kyle@moffetthome.net> 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.

I'm going to look into it.


Lars


\
 
 \ /
  Last update: 2009-05-04 18:19    [W:0.364 / U:0.108 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site