From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Max Waterman <davidmaxwaterman+kernel@fastmail.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: io performance...
Date: Mon, 16 Jan 2006 10:35:38 +0200 [thread overview]
Message-ID: <84144f020601160035y1ac037b2kfdc2ff4be5bacd79@mail.gmail.com> (raw)
In-Reply-To: <43CB4CC3.4030904@fastmail.co.uk>
Hi,
On 1/16/06, Max Waterman <davidmaxwaterman+kernel@fastmail.co.uk> wrote:
> I've noticed that I consistently get better (read) numbers from kernel 2.6.8
> than from later kernels.
[snip]
> 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
>
> Any ideas to why this might be? Any other advice/help?
It would be helpful if you could isolate the exact changeset that
introduces the regression. You can use git bisect for that. Please
refer to the following URL for details:
http://www.kernel.org/pub/software/scm/git/docs/howto/isolate-bugs-with-bisect.txt
Also note that changeset for pre 2.6.11-rc2 kernels are in
old-2.6-bkcvs git tree. If you are new to git, you can find a good
introduction here: http://linux.yyz.us/git-howto.html. Thanks.
Pekka
next prev parent reply other threads:[~2006-01-16 8:35 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 [this message]
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
[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
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=84144f020601160035y1ac037b2kfdc2ff4be5bacd79@mail.gmail.com \
--to=penberg@cs.helsinki.fi \
--cc=davidmaxwaterman+kernel@fastmail.co.uk \
--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;
as well as URLs for NNTP newsgroup(s).