From: Peter Zijlstra <peterz@infradead.org>
To: Mike Frysinger <vapier@gentoo.org>
Cc: linux-kernel@vger.kernel.org,
uclinux-dist-devel@blackfin.uclinux.org,
Sonic Zhang <sonic.zhang@analog.com>,
David Howells <dhowells@redhat.com>
Subject: Re: [PATCH/RFC] NOMMU: drop page cache whenever any alloc fails due to low memory
Date: Tue, 14 Jul 2009 16:30:38 +0200 [thread overview]
Message-ID: <1247581838.7500.98.camel@twins> (raw)
In-Reply-To: <1247581357-20068-1-git-send-email-vapier@gentoo.org>
On Tue, 2009-07-14 at 10:22 -0400, Mike Frysinger wrote:
> From: Sonic Zhang <sonic.zhang@analog.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.
next prev parent reply other threads:[~2009-07-14 14:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-14 14:22 [PATCH/RFC] NOMMU: drop page cache whenever any alloc fails due to low memory Mike Frysinger
2009-07-14 14:30 ` Peter Zijlstra [this message]
2009-07-15 3:29 ` Zhang, Sonic
2009-07-15 6:38 ` Peter Zijlstra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1247581838.7500.98.camel@twins \
--to=peterz@infradead.org \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sonic.zhang@analog.com \
--cc=uclinux-dist-devel@blackfin.uclinux.org \
--cc=vapier@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.