From: "Mike Frysinger" <vapier.adi@gmail.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Aubrey <aubreylee@gmail.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
mel <mel@csn.ul.ie>, Andy Whitcroft <apw@shadowen.org>
Subject: Re: The VFS cache is not freed when there is not enough free memory to allocate
Date: Sun, 26 Nov 2006 20:34:02 -0500 [thread overview]
Message-ID: <8bd0f97a0611261734i292a5c14s196ae037608c2c32@mail.gmail.com> (raw)
In-Reply-To: <1164192171.5968.186.camel@twins>
On 11/22/06, Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
> Yes it does that, but there is no guarantee that those 50MB have a
> single 1M contiguous region amongst them.
right ... the testcase posted is more to quickly illustrate the
problem ... the requested size doesnt really matter, what does matter
is that we cant seem to reclaim memory from the VFS cache in scenarios
where the VFS cache is eating a ton of memory and we need some more
another scenario is where an application is constantly reading data
from a cd, re-encoding it to mp3, and then writing it to disk. the
VFS cache here quickly eats up the available memory.
-mike
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2006-11-27 1:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-22 7:51 Aubrey
2006-11-22 8:43 ` Peter Zijlstra
2006-11-22 10:02 ` Aubrey
2006-11-22 10:42 ` Peter Zijlstra
2006-11-22 11:09 ` Aubrey
2006-11-27 1:34 ` Mike Frysinger [this message]
2006-11-27 7:39 ` Nick Piggin
2006-11-29 7:17 ` Sonic Zhang
2006-11-29 9:27 ` Aubrey
2006-11-29 9:30 ` Nick Piggin
2006-11-30 12:54 ` Aubrey
2006-11-30 21:18 ` Nick Piggin
2006-12-01 10:00 ` Aubrey
2006-11-28 13:29 Robin Getz
2006-11-28 14:41 ` Nick Piggin
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=8bd0f97a0611261734i292a5c14s196ae037608c2c32@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=apw@shadowen.org \
--cc=aubreylee@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox