On Thu, May 09, 2013 at 10:06:28AM +0400, Glauber Costa wrote: > From: Dave Chinner <dchinner@xxxxxxxxxx> > > Now that we have an LRU list API, we can start to enhance the > implementation. This splits the single LRU list into per-node lists > and locks to enhance scalability. Items are placed on lists > according to the node the memory belongs to. To make scanning the > lists efficient, also track whether the per-node lists have entries > in them in a active nodemask. > > [ glommer: fixed warnings ] > Signed-off-by: Dave Chinner <dchinner@xxxxxxxxxx> > Signed-off-by: Glauber Costa <glommer@xxxxxxxxxx> > Reviewed-by: Greg Thelen <gthelen@xxxxxxxxxx> You've committed to addressing the problem of the size of struct list_lru so Acked-by: Mel Gorman <mgorman@xxxxxxx> It would still be nice though if the size problem was highlighted with either a comment and/or a changelog entry describing the problem and how you plan to address it in case it takes a long time to get fixed. If the problem persists and we get a bug report about allocation warnings at mount time then the notes will be available. -- Mel Gorman SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
