[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46CB55A8.4030501@redhat.com>
Date: Tue, 21 Aug 2007 17:14:16 -0400
From: Rik van Riel <riel@...hat.com>
To: Christoph Lameter <clameter@....com>
CC: linux-mm@...ck.org, linux-kernel@...r.kernel.org,
akpm@...ux-foundation.org, dkegel@...gle.com,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
David Miller <davem@...emloft.net>,
Nick Piggin <npiggin@...e.de>
Subject: Re: [RFC 0/7] Postphone reclaim laundry to write at high water marks
Christoph Lameter wrote:
> On Tue, 21 Aug 2007, Rik van Riel wrote:
>
>> Christoph Lameter wrote:
>>
>>> 1. First reclaiming non dirty pages. Dirty pages are deferred until reclaim
>>> has reestablished the high marks. Then all the dirty pages (the laundry)
>>> is written out.
>> That sounds like a horrendously bad idea. While one process
>> is busy freeing all the non dirty pages, other processes can
>> allocate those pages, leaving you with no memory to free up
>> the dirty pages!
>
> What is preventing that from occurring right now? If the dirty pags are
> aligned in the right way you can have the exact same situation.
For one, dirty page writeout is done even when free memory
is low. The kernel will dig into the PF_MEMALLOC reserves,
instead of deciding not to do writeout unless there is lots
of free memory.
Secondly, why would you want to recreate this worst case on
purpose every time the pageout code runs?
--
Politics is the struggle between those who want to make their country
the best in the world, and those who believe it already is. Each group
calls the other unpatriotic.
-
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