From: Dave Hansen <haveblue@us.ibm.com>
To: Alok Mooley <rangdi@yahoo.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Active defragmentation : A replacement for bigphysarea?
Date: Thu, 18 Mar 2004 09:17:01 -0800 [thread overview]
Message-ID: <1079630221.5789.1906.camel@nighthawk> (raw)
In-Reply-To: <20040317173607.31415.qmail@web9706.mail.yahoo.com>
On Wed, 2004-03-17 at 09:36, Alok Mooley wrote:
> I have implemented a memory defragmentation utility
> for linux kernel 2.6 based on the paper by Mr. Daniel
> Phillips.
> Can this utility be used instead of the bigphysarea
> patch, for requirements less than MAX_ORDER of
> allocation ?
> Can the people using the bigphysarea patch kindly
> provide me with their respective memory requirements.
Have you incorporated any of the suggestions from the last time that you
posted the patch? Could you post the current version?
-- dave
next prev parent reply other threads:[~2004-03-18 17:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-17 17:36 Active defragmentation : A replacement for bigphysarea? Alok Mooley
2004-03-18 15:42 ` Rik van Riel
2004-03-19 3:17 ` Alok Mooley
2004-03-18 17:17 ` Dave Hansen [this message]
2004-03-19 3:12 ` Alok Mooley
-- strict thread matches above, loose matches on Subject: below --
2004-03-16 14:08 vijay agashe
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=1079630221.5789.1906.camel@nighthawk \
--to=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rangdi@yahoo.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