From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Kurt Fitzner <kfitzner@excelcia.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.5-mm5
Date: Tue, 13 Apr 2004 17:56:05 +1000 [thread overview]
Message-ID: <407B9D15.2010804@yahoo.com.au> (raw)
In-Reply-To: <407B990A.8050407@excelcia.org>
Kurt Fitzner wrote:
> Andrew Morton wrote:
>
>>
>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.5/2.6.5-mm5/
>>
>>
>> - More CPU scheduler work. Hopefully this kernel will now address the
>> regressions that a few people have noted on certain workloads. We
>> appear to
>> be getting close.
>
>
> Regressions... from the context, I'm assuming you're not talking
> regression errors here? I'm assuming these are performance issues? I
> see a 3.5% drop in compiling speed between 2.4.24 and 2.6.5 on a dual
> Athlon workstation. I'll test this kernel happily if the scheduler
> tweaks are intended to address this.
>
Hi Kurt,
The context was actually sched-domains regressions vs numasched,
which might possibly arise in any SMP (even simple dual) system.
So in this case we are interested in -mm regressions compared to
the official 2.6 tree.
2.6 regressions versus 2.4 are still interesting, but a 3.5% drop
in kernel compiling is probably due to HZ=1000 and rmap, although
I think you can expect improvements in rmap overhead soon... try
2.6.5-aa5 if you are interested.
next prev parent reply other threads:[~2004-04-13 7:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-13 5:17 2.6.5-mm5 Andrew Morton
2004-04-13 7:38 ` 2.6.5-mm5 Kurt Fitzner
2004-04-13 7:56 ` Nick Piggin [this message]
2004-04-13 8:07 ` 2.6.5-mm5 devpts filesystem doesn't work Helge Hafting
2004-04-13 8:11 ` Andrew Morton
2004-04-13 8:36 ` Sean Neakums
2004-04-13 8:39 ` Andrew Morton
2004-04-13 9:19 ` Marc-Christian Petersen
2004-04-13 9:26 ` Andrew Morton
2004-04-14 12:38 ` Helge Hafting
2004-04-13 11:36 ` 2.6.5-mm5: no help text for S2IO_NAPI Adrian Bunk
2004-04-13 16:02 ` 2.6.5-mm5 (compile stats) John Cherry
2004-04-15 15:30 ` 2.6.5-mm5 markw
2004-04-15 19:42 ` 2.6.5-mm5 Andrew Morton
2004-04-16 14:51 ` 2.6.5-mm5 markw
2004-04-16 22:59 ` 2.6.5-mm5 Nick Piggin
2004-04-16 23:03 ` 2.6.5-mm5 markw
2004-04-18 9:20 ` 2.6.5-mm5 Nick Piggin
2004-04-19 14:53 ` 2.6.5-mm5 markw
2004-04-19 14:51 ` 2.6.5-mm5 markw
2004-04-16 1:57 ` 2.6.5-mm5 Nick Piggin
2004-04-16 10:34 ` 2.6.5-mm5 Ingo Molnar
2004-04-16 14:52 ` 2.6.5-mm5 markw
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=407B9D15.2010804@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=kfitzner@excelcia.org \
--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