linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Scott F. H. Kaplan" <sfkaplan@algol.cs.amherst.edu>
To: linux-mm@kvack.org
Subject: Re: How to fix the total size of buffer caches in 2.4.5?
Date: Wed, 11 Jun 2003 23:36:26 -0400	[thread overview]
Message-ID: <20030611233626.A30212@algol.cs.amherst.edu> (raw)
In-Reply-To: <20030611165017.GS15692@holomorphy.com>; from wli@holomorphy.com on Wed, Jun 11, 2003 at 09:50:17AM -0700

On Wed, Jun 11, 2003 at 09:50:17AM -0700, William Lee Irwin III wrote:
> On Wed, Jun 11, 2003 at 12:28:18PM -0400, Shansi Ren wrote:
> > 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.
> 
> That's actually too old, not too new.

On this point, I definitely agree.

> Also, 2.4.x is relatively deeply frozen. I won't consult Marcelo (he
> has enough to deal with), but IMHO it's not productive to demonstrate
> major design changes against a codebase that can (by definition) never
> absorb them. i.e. it'd be best to try to work against current 2.5.x.

On this point, I disagree.  Given Shansi's goal of ``doing a research
project'', choosing a stable, documented kernel may be a better idea
than a developmental kernel.  I may misinterpret the aim of this work,
but based on the description (comparing a new page replacement
algorithm against LRU), it seems unlikely that the immediate goal is
to implement ``major design changes'' that can be aborbed into a
codebase.  It seems that the intention is simply to use Linux as an
experimental platform to gather results for page replacment policy
comparisons.

If I am understanding your situation correctly, Shansi, please let me
know.  For my projects, I've done some of the groundwork of
implementing a more ``classical'' global LRU approximation.  It may
provide you a simpler framework for implementing your own page
replacement policy.  Since my goal is to obtain experimental results
for a research project, and not necessarily to produce code that would
be adopted into the kernel, it may be appropriate for your purposes.
My work is based on the 2.4.20 kernel, which is close to (and may
still be) the latest 2.4.x kernel.

If I am completely off the mark, then forgive me!

Scott
--
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>

  reply	other threads:[~2003-06-12  3:36 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
2003-06-11 16:50     ` William Lee Irwin III
2003-06-12  3:36       ` Scott F. H. Kaplan [this message]
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=20030611233626.A30212@algol.cs.amherst.edu \
    --to=sfkaplan@algol.cs.amherst.edu \
    --cc=linux-mm@kvack.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