From: Max Waterman <davidmaxwaterman+kernel@fastmail.co.uk>
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: io performance...
Date: Thu, 19 Jan 2006 21:18:19 +0800 [thread overview]
Message-ID: <43CF919B.1020902@fastmail.co.uk> (raw)
In-Reply-To: <20060119004853.GP19398@stusta.de>
Unfortunately, they don't want me to spend time doing this sort of
thing, so I'm out of luck.
They're going to stick with 2.6.8-smp, which seems to give the best
performance (which rules out your second case below, I suppose).
:|
Max.
Adrian Bunk wrote:
> On Mon, Jan 16, 2006 at 03:35:31PM +0800, Max Waterman wrote:
>> Hi,
>>
>> I've been referred to this list from the linux-raid list.
>>
>> I've been playing with a RAID system, trying to obtain best bandwidth
>> from it.
>>
>> I've noticed that I consistently get better (read) numbers from kernel 2.6.8
>> than from later kernels.
>>
>> For example, I get 135MB/s on 2.6.8, but I typically get ~90MB/s on later
>> kernels.
>>
>> I'm using this :
>>
>> <http://www.sharcnet.ca/~hahn/iorate.c>
>>
>> to measure the iorate. I'm using the debian distribution. The h/w is a
>> MegaRAID
>> 320-2. The array I'm measuring is a RAID0 of 4 Fujitsu Max3073NC 15Krpm
>> drives.
>>
>> The later kernels I've been using are :
>>
>> 2.6.12-1-686-smp
>> 2.6.14-2-686-smp
>> 2.6.15-1-686-smp
>>
>> The kernel which gives us the best results is :
>>
>> 2.6.8-2-386
>>
>> (note that it's not an smp kernel)
>>
>> I'm testing on an otherwise idle system.
>>
>> Any ideas to why this might be? Any other advice/help?
>
> You should try to narrow the problem a bit down.
>
> Possible causes are:
> - kernel regression between 2.6.8 and 2.6.12
> - SMP <-> !SMP support
> - patches and/or configuration changes in the Debian kernels
>
> You should try self-compiled unmodified 2.6.8 and 2.6.12 ftp.kernel.org
> kernels with the same .config (modulo differences by "make oldconfig").
>
> After this test, you know whether you are in the first case.
> If yes, you could do a bisect search for finding the point where the
> regression started.
>
>> Thanks!
>>
>> Max.
>
> cu
> Adrian
>
next prev parent reply other threads:[~2006-01-19 13:18 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-16 7:35 io performance Max Waterman
2006-01-16 7:32 ` Jeff V. Merkey
2006-01-17 13:57 ` Jens Axboe
2006-01-17 19:17 ` Jeff V. Merkey
2006-01-16 8:35 ` Pekka Enberg
2006-01-17 17:06 ` Phillip Susi
2006-01-18 7:24 ` Max Waterman
2006-01-18 15:19 ` Phillip Susi
2006-01-20 5:58 ` Max Waterman
2006-01-20 13:42 ` Ian Soboroff
2006-01-25 6:36 ` Max Waterman
2006-01-25 14:19 ` Ian Soboroff
2006-01-25 13:09 ` Bernd Eckenfels
2006-01-18 3:02 ` Max Waterman
2006-01-18 4:30 ` Jeff V. Merkey
2006-01-18 5:09 ` Max Waterman
2006-01-18 4:37 ` Jeff V. Merkey
2006-01-18 7:06 ` Max Waterman
2006-01-18 9:21 ` Alan Cox
2006-01-18 15:48 ` Phillip Susi
2006-01-18 16:25 ` Bartlomiej Zolnierkiewicz
2006-01-19 0:48 ` Adrian Bunk
2006-01-19 13:18 ` Max Waterman [this message]
[not found] <5vx8f-1Al-21@gated-at.bofh.it>
[not found] ` <5wbRY-3cF-3@gated-at.bofh.it>
[not found] ` <5wdKh-5wF-15@gated-at.bofh.it>
2006-01-19 1:58 ` Robert Hancock
2006-01-19 13:14 ` Max Waterman
2006-01-19 14:08 ` Alan Cox
2006-01-20 4:09 ` Max Waterman
2006-01-20 4:27 ` Alexander Samad
2006-01-20 12:52 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2006-01-19 11:39 Al Boldi
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=43CF919B.1020902@fastmail.co.uk \
--to=davidmaxwaterman+kernel@fastmail.co.uk \
--cc=bunk@stusta.de \
--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