From: "Downing, Thomas" <Thomas.Downing@ipc.com>
To: Andrew Morton <akpm@digeo.com>, linux-mm@kvack.org
Subject: RE: 2.5.70-mm1
Date: Wed, 28 May 2003 09:26:32 -0400 [thread overview]
Message-ID: <170EBA504C3AD511A3FE00508BB89A92021C912E@exnanycmbx4.ipc.com> (raw)
-----Original Message-----
From: Andrew Morton [mailto:akpm@digeo.com]
>
> http://www.zip.com.au/~akpm/linux/patches/2.5/2.5.70-mm1.gz
>
> Will appear soon at
>
>
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.5/2.5.70/2.5.70-
mm1/
>
> . A number of fixes against the ext3 work which Alex and I have been
doing.
> This code is stable now. I'm using it on my main SMP desktop machine.
>
> These are major changes to a major filesystem. I would ask that
> interested parties now subject these patches to stresstesting and to
> performance testing. The performance gains on SMP will be significant.
[snip]
Running this version for 2 days now on heavily used build machine.
No problems to report. Here are some numbers for kernel build.
Machine is SMP, 2 Xeon P4, Intel chipset, single IDE HD, with
hyperthreading enabled.
2.5.67-bk4 (i think bk4):
make -j1 make -j4
-------- --------
real 5m03.889 2m37.253
user 4m27.550 4m41.037
sys 0m27.727 0m29.651
2.5.70-mm1:
make -j1 make -j4
-------- --------
real 4m52.212 2m41.565
user 4m27.447 4m40.462
sys 0m29.079 0m31.184
This test does not show any significant difference. On the other hand,
even with -j4 the disk activity is light. If you have a better test
that you would like me to run, point me to it, and I'll do it.
--
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 reply other threads:[~2003-05-28 13:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-28 13:26 Downing, Thomas [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-27 7:42 2.5.70-mm1 Andrew Morton
2003-05-27 10:38 ` 2.5.70-mm1 Marc-Christian Petersen
2003-05-27 20:33 ` 2.5.70-mm1 Ed Tomlinson
2003-05-27 20:49 ` 2.5.70-mm1 Andrew Morton
2003-05-27 23:05 ` 2.5.70-mm1 Ed Tomlinson
2003-05-28 17:10 ` 2.5.70-mm1 Mingming Cao
2003-05-28 19:44 ` 2.5.70-mm1 Andrew Morton
2003-05-29 6:23 ` 2.5.70-mm1 Martin J. Bligh
2003-05-29 18:40 ` 2.5.70-mm1 Martin J. Bligh
2003-05-29 18:52 ` 2.5.70-mm1 Andrew Morton
2003-05-29 20:30 ` 2.5.70-mm1 Martin J. Bligh
2003-05-29 21:14 ` 2.5.70-mm1 Andrew Morton
2003-05-30 15:51 ` 2.5.70-mm1 Martin J. Bligh
2003-05-30 16:43 ` 2.5.70-mm1 Andrew Morton
2003-05-30 23:51 ` 2.5.70-mm1 Martin J. Bligh
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=170EBA504C3AD511A3FE00508BB89A92021C912E@exnanycmbx4.ipc.com \
--to=thomas.downing@ipc.com \
--cc=akpm@digeo.com \
--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