lkml.org 
[lkml]   [2013]   [Jan]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [RFC, PATCH 00/19] Numa aware LRU lists and shrinkers
    On 11/28/2012 03:14 AM, Dave Chinner wrote:
    > [PATCH 09/19] list_lru: per-node list infrastructure
    >
    > This makes the generic LRU list much more scalable by changing it to
    > a {list,lock,count} tuple per node. There are no external API
    > changes to this changeover, so is transparent to current users.
    >
    > [PATCH 10/19] shrinker: add node awareness
    > [PATCH 11/19] fs: convert inode and dentry shrinking to be node
    >
    > Adds a nodemask to the struct shrink_control for callers of
    > shrink_slab to set appropriately for their reclaim context. This
    > nodemask is then passed by the inode and dentry cache reclaim code
    > to the generic LRU list code to implement node aware shrinking.

    I have a follow up question that popped up from a discussion between me
    and my very American friend Johnny Wheeler, also known as Johannes
    Weiner (CC'd). I actually remember we discussing this, but don't fully
    remember the outcome. And since I can't find it anywhere, it must have
    been in a media other than e-mail. So I thought it would do no harm in
    at least documenting it...

    Why are we doing this per-node, instead of per-zone?

    It seems to me that the goal is to collapse all zones of a node into a
    single list, but since the number of zones is not terribly larger than
    the number of nodes, and zones is where the pressure comes from, what do
    we really gain from this?



    \
     
     \ /
      Last update: 2013-01-21 17:44    [W:7.645 / U:0.184 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site