From: Jesse Barnes <jbarnes@engr.sgi.com>
To: krmurthy@cisco.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Limiting memory allocated by buffer cache in 2.4 kernel
Date: Wed, 15 Dec 2004 09:56:23 -0800 [thread overview]
Message-ID: <200412150956.23799.jbarnes@engr.sgi.com> (raw)
In-Reply-To: <013901c4e2b4$bd041ad0$f8074d0a@apac.cisco.com>
On Wednesday, December 15, 2004 6:45 am, N.C.Krishna Murthy (krmurthy) wrote:
> Hi,
> I am using linux 2.4.22 kernel. Is there any way to limit the amount
> of memory allocated by buffer cache? Eariler versions used to have
> /proc/sys/vm/buffermem.
For that matter, is there a way to do this in 2.6? We've seen problems caused
by huge page caches pushing data allocations off-node, so it would be really
nice to have a limit control...
Jesse
next prev parent reply other threads:[~2004-12-15 17:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-15 14:45 Limiting memory allocated by buffer cache in 2.4 kernel N.C.Krishna Murthy (krmurthy)
2004-12-15 17:56 ` Jesse Barnes [this message]
2004-12-16 9:14 ` Marcelo Tosatti
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=200412150956.23799.jbarnes@engr.sgi.com \
--to=jbarnes@engr.sgi.com \
--cc=krmurthy@cisco.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox