From: Shansi Ren <sren@CS.WM.EDU>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: linux-mm@kvack.org
Subject: Re: How to fix the total size of buffer caches in 2.4.5?
Date: Wed, 11 Jun 2003 12:28:18 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0306111226160.1656-100000@ickis.cs.wm.edu> (raw)
In-Reply-To: <20030611162224.GR15692@holomorphy.com>
What version do you suggest then? The reason why I choose 2.4.5 is that
I'm doing a research project. Experiments on earlier versions may not be
persuasive to audience.
On Wed, 11 Jun 2003, William Lee Irwin III wrote:
> On Wed, Jun 11, 2003 at 12:13:34PM -0400, Shansi Ren wrote:
> > I'm trying to implement the pure LRU algorithm and a new page
> > replacement algorithm on top of 2.4.5 kernel, and compare their
> > performance. Can anybody tell me if there is an easy way to seperate the
> > buffer cache management from the virtual memory management? And how to
> > preallocate a chunk of memory for buffer cache usage exclusively, say,
> > 32M exclusively for buffer cache? Thanks.
>
> What kernel version did you really mean? 2.4.5 sounds implausible to be
> what you're really working against.
>
>
> -- wli
> --
> 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:"aart@kvack.org"> aart@kvack.org </a>
>
--
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:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2003-06-11 16:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-11 16:13 Shansi Ren
2003-06-11 16:22 ` William Lee Irwin III
2003-06-11 16:28 ` Shansi Ren [this message]
2003-06-11 16:50 ` William Lee Irwin III
2003-06-12 3:36 ` Scott F. H. Kaplan
2003-06-12 4:07 ` William Lee Irwin III
2003-06-12 4:52 ` Shansi Ren
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=Pine.LNX.4.44.0306111226160.1656-100000@ickis.cs.wm.edu \
--to=sren@cs.wm.edu \
--cc=linux-mm@kvack.org \
--cc=wli@holomorphy.com \
/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