[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4a5909270708101625q407a240ck6109ef536fdbed4a@mail.gmail.com>
Date: Fri, 10 Aug 2007 19:25:34 -0400
From: "Daniel Phillips" <daniel.raymond.phillips@...il.com>
To: "Christoph Lameter" <clameter@....com>
Cc: "Daniel Phillips" <phillips@...nq.net>,
"Peter Zijlstra" <a.p.zijlstra@...llo.nl>,
"Matt Mackall" <mpm@...enic.com>, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, "David Miller" <davem@...emloft.net>,
"Andrew Morton" <akpm@...ux-foundation.org>,
"Daniel Phillips" <phillips@...gle.com>
Subject: Re: [PATCH 02/10] mm: system wide ALLOC_NO_WATERMARK
On 8/10/07, Christoph Lameter <clameter@....com> wrote:
> The idea of adding code to deal with "I have no memory" situations
> in a kernel that based on have as much memory as possible in use at all
> times is plainly the wrong approach.
No. It is you who have read the patches wrongly, because what you
imply here is exactly backwards.
> If you need memory then memory needs
> to be reclaimed. That is the basic way that things work
Wrong. A naive reading of your comment would suggest you do not
understand how PF_MEMALLOC works, and that it has worked that way from
day one (well, since long before I arrived) and that we just do more
of the same, except better.
> and following that
> through brings about a much less invasive solution without all the issues
> that the proposed solution creates.
What issues? Test case please, a real one that you have run yourself.
Please, no more theoretical issues that cannot be demonstrated in
practice because they do not exist.
Regards,
Daniel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists