From: William Lee Irwin III <wli@holomorphy.com>
To: Andi Kleen <ak@suse.de>
Cc: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>,
Henti Smith <bain@tcsn.co.za>,
linux-kernel@vger.kernel.org, lse-tech@lists.sourceforge.net
Subject: Re: [Lse-tech] Re: maximum possible memory limit ..
Date: Mon, 28 Apr 2003 21:02:47 -0700 [thread overview]
Message-ID: <20030429040247.GF30441@holomorphy.com> (raw)
In-Reply-To: <20030428151648.GF4525@Wotan.suse.de>
On Mon, Apr 28, 2003 at 05:16:49PM +0200, Andi Kleen wrote:
> Nobody is doing that. pgcl is 2.5 only and seems to be still quite instable.
> Also it's extremly intrusive.
Unfortunately true. For all the merits of the technique itself, I'm not
hugh, and my results are proportionally less impressive.
That said, the intrusiveness aspect is easily dealt with as the patch
itself is very easy to chop into small pieces and merge incrementally.
I'd also say my progress toward stabilization is steady, though, of
course, things are by no means perfect.
At this point I'm literally more concerned about cleanliness than pure
stability, as the stability aspects lacking appear to be related
primarily to sweeping through code I can't regularly test anyway. After
that, of course, due diligence demands the driver sweeps etc. be
carried out before fully merging, but it's ultimately busywork. Not to
say it's any less essential, for a kernel would be useless without
drivers, but that's what it is.
If this is not your experience, I'd love to hear things like bugreports
and so on. Whatever feedback I can get I'd be very grateful for. I feel
that the highmem emphasis of my own particular effort has marginalized
the patch, and no one's really trying it out for things like large fs
blocksize and the linear space reductions and speedups. Of course, that
may be partially due to the fact I've not merged some of the things
needed to properly combat fragmentation into the patch, but those will
be taken care of in the next 72-96 hours (if they're not and I can't
write about them ajh will strangle me, but I've already taken care of
most of it anyway, and just haven't posted a release with the stuff).
-- wli
next prev parent reply other threads:[~2003-04-29 3:50 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-24 18:05 maximum possible memory limit Henti Smith
2003-04-24 18:35 ` Valdis.Kletnieks
2003-04-28 13:08 ` Carl-Daniel Hailfinger
2003-04-28 14:10 ` [Lse-tech] " Andi Kleen
2003-04-28 15:11 ` Carl-Daniel Hailfinger
2003-04-28 15:16 ` Andi Kleen
2003-04-28 16:52 ` Dave Hansen
2003-04-28 16:58 ` Martin J. Bligh
2003-04-28 22:40 ` William Lee Irwin III
2003-04-28 23:50 ` Dave Jones
2003-04-29 0:00 ` William Lee Irwin III
2003-04-29 0:06 ` Dave Jones
2003-04-29 0:13 ` William Lee Irwin III
2003-04-28 22:34 ` William Lee Irwin III
2003-04-28 22:33 ` William Lee Irwin III
2003-04-29 4:02 ` William Lee Irwin III [this message]
2003-04-28 16:45 ` Dave Hansen
2003-04-28 16:57 ` Carl-Daniel Hailfinger
2003-04-28 17:13 ` Andi Kleen
2003-04-28 17:53 ` David Mosberger
2003-04-28 18:31 ` Gerrit Huizenga
2003-04-28 19:05 ` David Mosberger
2003-04-28 17:16 ` Dave Hansen
2003-04-28 17:36 ` Carl-Daniel Hailfinger
2003-04-28 17:44 ` Andi Kleen
2003-04-28 22:43 ` William Lee Irwin III
2003-04-28 22:43 ` William Lee Irwin III
2003-04-28 18:57 ` Anton Blanchard
2003-04-28 17:14 ` Andi Kleen
2003-04-28 17:26 ` Dave Hansen
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=20030429040247.GF30441@holomorphy.com \
--to=wli@holomorphy.com \
--cc=ak@suse.de \
--cc=bain@tcsn.co.za \
--cc=c-d.hailfinger.kernel.2003@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
/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