From: "Martin J. Bligh" <mbligh@aracnet.com>
To: haiquy@yahoo.com, linux-kernel@vger.kernel.org
Subject: Re: linux-2.6.5-mjb1 Comment.
Date: Wed, 14 Apr 2004 16:45:54 -0700 [thread overview]
Message-ID: <166840000.1081986354@flay> (raw)
In-Reply-To: <Pine.LNX.4.53.0404150815250.654@linuxcd>
> Test 2.6.5-mjb2 for more than 2 days only, system is pretty stable (the same as
> almost all other 2.6.x with my box). The significant performance improved
> compared to 2.6.5-aa5, 2.6.5 and all others 2.6.x for with a low end box line mine
> (660 Mhx Celeron 256 Mb RAM) make me write this comment. :-) Wish that some
> improvement could make way to the mainline kernel.
Good ;-) We're working on getting it integrated back in ... just a couple of
outstanding corner cases need killing first.
> The memory management is nearly perfect. Before I tried one ck kernel use auto
> regulation swap and it was still much worse than this one as I noticed the value
> in swappiness also changes by the time.
Con's changes are in there, but they were updated once or twice, and there
are bug fixes too. I still think it's the Right Thing to Do (tm).
M.
prev parent reply other threads:[~2004-04-14 23:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-15 8:31 linux-2.6.5-mjb1 Comment haiquy
2004-04-14 23:45 ` Martin J. Bligh [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=166840000.1081986354@flay \
--to=mbligh@aracnet.com \
--cc=haiquy@yahoo.com \
--cc=linux-kernel@vger.kernel.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