[lkml]   [2007]   [Sep]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] prevent kswapd from freeing excessive amounts of lowmem
Andrew Morton wrote:
>> On Thu, 06 Sep 2007 12:38:13 -0400 Rik van Riel <> wrote:
>> Andrew Morton wrote:
> (What happened to the other stuff I said?)

Mlock can cause the problem too. As for all_unreclaimable,
it is ignored when priority == DEF_PRIORITY, balance_pgdat
always seems to start in this stage.

>>> I guess for a very small upper zone and a very large lower zone this could
>>> still put the scan balancing out of whack, fixable by a smarter version of
>>> "8*zone->pages_high" but it doesn't seem very likely that this will affect
>>> things much.
>>> Why doesn't direct reclaim need similar treatment?
>> Because we only go into the direct reclaim path once
>> every zone is at or below zone->pages_low, and the
>> direct reclaim path will exit once we have freed more
>> than swap_cluster_max pages.
> hm. Now I need to remember why direct-reclaim does that :(

This is done so the system does not end up with the first
process that goes into page reclaim staying there forever,
while the other processes in the system happily consume
the pages freed by that poor first process.

There may be other reasons, too.

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
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2007-09-07 00:51    [W:0.038 / U:2.956 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site