From: William Lee Irwin III <wli@holomorphy.com>
To: "Scott F. H. Kaplan" <sfkaplan@algol.cs.amherst.edu>
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 21:07:30 -0700 [thread overview]
Message-ID: <20030612040730.GX15692@holomorphy.com> (raw)
In-Reply-To: <20030611233626.A30212@algol.cs.amherst.edu>
On Wed, Jun 11, 2003 at 11:36:26PM -0400, Scott F. H. Kaplan wrote:
> 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.
This was in no small part a reaction to the backportmania and
proliferation of grossly inappropriate patches against the stable
series of the past several years. IMHO, it is a justified one.
If the goals are truly limited to using 2.4.x as a pure research
vehicle, I say there are no holds barred. But experience is the mother
of pessimism, and I'd rather keep it on the pill than see another
litter of 2.4.x-based core subsystem rewrites or "dev trees" hatched.
-- 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>
next prev parent reply other threads:[~2003-06-12 4:07 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
2003-06-12 4:07 ` William Lee Irwin III [this message]
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=20030612040730.GX15692@holomorphy.com \
--to=wli@holomorphy.com \
--cc=linux-mm@kvack.org \
--cc=sfkaplan@algol.cs.amherst.edu \
/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