From: Nick Piggin <nickpiggin@yahoo.com.au>
To: jmerkey <jmerkey@utah-nac.org>
Cc: Jeff Garzik <jgarzik@pobox.com>,
"Chen, Kenneth W" <kenneth.w.chen@intel.com>,
linux-kernel@vger.kernel.org, Jens Axboe <axboe@suse.de>
Subject: Re: kernel performance update - 2.6.14
Date: Sat, 29 Oct 2005 18:38:31 +1000 [thread overview]
Message-ID: <43633507.2050006@yahoo.com.au> (raw)
In-Reply-To: <4362E7B3.6020509@utah-nac.org>
jmerkey wrote:
> jmerkey wrote:
>> Yes I did. The list wasn't too long. I had problems with RCU messages
>> and irq warn messages at very high loads and init respawning itself
>> subjected to loads > 369 MB/S to the disk channels on 2.6.13.
>> Performance was down on disk I/O [vs.] 2.6.9. I did not investigate
>> the BIO fixes but something changed there. Theres also some memory
>> problems with corruption somewhere in the 2.6.14 (during module unload
>> and shutdown).
>>
Well that doesn't sound too good. It would be good if you could document
and report each problem - the messages, workload, kernel config and any
patches used, etc. And post them to lkml. Hopefully they can get sorted
out.
Thanks,
Nick
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
next prev parent reply other threads:[~2005-10-29 8:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-28 23:44 kernel performance update - 2.6.14 Chen, Kenneth W
2005-10-28 23:54 ` Jeff Garzik
2005-10-28 22:43 ` Jeff V. Merkey
2005-10-29 2:49 ` Nick Piggin
2005-10-29 3:06 ` jmerkey
2005-10-29 3:08 ` jmerkey
2005-10-29 3:15 ` jmerkey
2005-10-29 8:38 ` Nick Piggin [this message]
2005-10-29 0:04 ` Chen, Kenneth W
2005-10-29 0:19 ` Felix Oxley
2005-10-29 0:29 ` Felix Oxley
2005-10-29 0:42 ` Chen, Kenneth W
2005-10-29 11:17 ` Dr. David Alan Gilbert
2005-10-29 0:29 ` Chen, Kenneth W
-- strict thread matches above, loose matches on Subject: below --
2005-11-08 0:04 Chen, Tim C
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=43633507.2050006@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=axboe@suse.de \
--cc=jgarzik@pobox.com \
--cc=jmerkey@utah-nac.org \
--cc=kenneth.w.chen@intel.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