From: Shansi Ren <sren@CS.WM.EDU>
To: linux-mm@kvack.org
Subject: Re: How to fix the total size of buffer caches in 2.4.5?
Date: Thu, 12 Jun 2003 00:52:55 -0400 (EDT) [thread overview]
Message-ID: <3224.68.10.230.122.1055393575.squirrel@www.cs.wm.edu> (raw)
In-Reply-To: <20030611233626.A30212@algol.cs.amherst.edu>
>> 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.
That's exactly what I intend to do. I just want to use Linux as a
platform, and do as little modification to the codebase as possible.
Your help are highly appreciated.
--
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>
prev parent reply other threads:[~2003-06-12 4:52 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
2003-06-12 4:52 ` Shansi Ren [this message]
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=3224.68.10.230.122.1055393575.squirrel@www.cs.wm.edu \
--to=sren@cs.wm.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