lkml.org 
[lkml]   [2005]   [Jan]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH][5/?] count writeback pages in nr_scanned
On Wed, 5 Jan 2005, Andrew Morton wrote:
> Rik van Riel <riel@redhat.com> wrote:

>> The recent OOM kill problem has been happening:
>> 1) with cache pressure on lowmem only, due to a block device write
>> 2) with no block congestion at all
>> 3) with pretty much all pageable lowmme pages in writeback state
>
> You must have a wild number of requests configured in the queue. Is
> this CFQ?

Yes, it is with CFQ. Around 650MB of lowmem is in writeback
stage, which is over 99% of the active and inactive lowmem
pages...

> I've done testing with "all of memory under writeback" before and it
> went OK. It's certainly a design objective to handle this well. But
> that testing was before we broke it.

I suspect something might still be broken. It may take a few
days of continuous testing to trigger the bug, though ...

> The bug which you fixed would cause the VM to scan itself to death
> without throttling. Did the fix fix things?

Mostly fixed. Things are down to the point where it often
takes over a day to bring out the bug.

--
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 14:09    [W:0.184 / U:0.404 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site