linux-kernel - Re: [PATCH] prevent kswapd from freeing excessive amounts of lowmem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20070906153426.a173f8e2.akpm@linux-foundation.org>
Date:	Thu, 6 Sep 2007 15:34:26 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Rik van Riel <riel@...hat.com>
Cc:	linux-kernel@...r.kernel.org, linux-mm@...ck.org,
	safari-kernel@...ari.iki.fi
Subject: Re: [PATCH] prevent kswapd from freeing excessive amounts of lowmem

> On Thu, 06 Sep 2007 12:38:13 -0400 Rik van Riel <riel@...hat.com> wrote:
> Andrew Morton wrote:
> 

(What happened to the other stuff I said?)

> > 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 :(
-
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/