lkml.org 
[lkml]   [2008]   [Feb]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH 00/28] Swap over NFS -v16
From
Date

On Tue, 2008-02-26 at 11:50 +0100, Peter Zijlstra wrote:

> > mm-reserve.patch
> >
> > I'm confused by __mem_reserve_add.
> >
> > + reserve = mem_reserve_root.pages;
> > + __calc_reserve(res, pages, 0);
> > + reserve = mem_reserve_root.pages - reserve;
> >
> > __calc_reserve will always add 'pages' to mem_reserve_root.pages.
> > So this is a complex way of doing
> > reserve = pages;
> > __calc_reserve(res, pages, 0);
> >
> > And as you can calculate reserve before calling __calc_reserve
> > (which seems odd when stated that way), the whole function looks
> > like it could become:
> >
> > ret = adjust_memalloc_reserve(pages);
> > if (!ret)
> > __calc_reserve(res, pages, limit);
> > return ret;
> >
> > What am I missing?
>
> Probably the horrible twist my brain has. Looking at it makes me doubt
> my own sanity. I think you're right - it would also clean up
> __calc_reserve() a little.
>
> This is what review for :-)

Ah, you confused me. Well, I confused me - this does deserve a comment
its tricksy.

Its correct. The trick is, the mem_reserve in question (res) need not be
connected to mem_reserve_root.

In that case, mem_reserve_root.pages will not change, but we do
propagate the change as far up as possible, so that
mem_reserve_connect() can just observe the parent and child without
being bothered by the rest of the hierarchy.





\
 
 \ /
  Last update: 2008-02-26 13:05    [W:1.496 / U:0.404 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site