linux-kernel - RE: [PATCH/RFC] NOMMU: drop page cache whenever any alloc fails due to low memory

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] [day] [month] [year] [list]

Date:	Wed, 15 Jul 2009 08:38:03 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	"Zhang, Sonic" <Sonic.Zhang@...log.com>
Cc:	Mike Frysinger <vapier@...too.org>, linux-kernel@...r.kernel.org,
	uclinux-dist-devel@...ckfin.uclinux.org,
	David Howells <dhowells@...hat.com>
Subject: RE: [PATCH/RFC] NOMMU: drop page cache whenever any alloc fails
 due to low memory

Please don't top post.

On Wed, 2009-07-15 at 11:29 +0800, Zhang, Sonic wrote:

> From: Peter Zijlstra [mailto:peterz@...radead.org] 
> > Sent: Tuesday, July 14, 2009 10:31 PM
> > To: Mike Frysinger
> > Cc: linux-kernel@...r.kernel.org;
> > uclinux-dist-devel@...ckfin.uclinux.org; Zhang, Sonic; David Howells
> > Subject: Re: [PATCH/RFC] NOMMU: drop page cache whenever any alloc fails
> > due to low memory
> > 
> > On Tue, 2009-07-14 at 10:22 -0400, Mike Frysinger wrote:
> > > From: Sonic Zhang <sonic.zhang@...log.com>
> > > 
> > > Since no-mmu systems tend to be memory constrained, we want to drop 
> > > all of the page cache whenever memory gets low.  The only other option
> > 
> > > is to invoke the oom killer, and clearly that's not ideal.
> > 
> > Uhm,.. normally reclaim will already try to drop pagecache.

> The reclaim is not that aggressive.

Well, then maybe we should fix that instead?
--
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/