From: Jens Axboe <axboe@suse.de>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: Bill Davidsen <davidsen@tmr.com>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: Linux v2.4.19-rc5
Date: Tue, 6 Aug 2002 10:48:51 +0200 [thread overview]
Message-ID: <20020806084851.GC1164@suse.de> (raw)
In-Reply-To: <Pine.NEB.4.44.0208061024570.27501-100000@mimas.fachschaften.tu-muenchen.de>
On Tue, Aug 06 2002, Adrian Bunk wrote:
> On Tue, 6 Aug 2002, Jens Axboe wrote:
>
> >...
> > try a work load that excercises the block i/o layer alone (O_DIRECT,
> > raw, whatnot) and then compare 2.4 and 2.5. ibm had some slides on this
> > from ols, unfortunately I don't know if they have then online.
> >...
>
> Pages 390-406 in
>
> http://www.linux.org.uk/~ajh/ols2002_proceedings.pdf.gz
>
> or are you talking about something different?
Right thanks, exactly those. Table 3 on page 395 is the one I noted.
Forget readv, as that hasn't been done in 2.5 yet. I'd say a 2.5.17
untweaked kernel beating 2.4 tweaked beyond recognition isn't too shabby
for a devel series kernel.
--
Jens Axboe
next prev parent reply other threads:[~2002-08-06 8:45 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-01 6:38 Linux v2.4.19-rc5 Marcelo Tosatti
2002-08-01 7:49 ` Jens Axboe
2002-08-01 7:14 ` Marcelo Tosatti
2002-08-01 8:10 ` Jens Axboe
2002-08-01 9:02 ` Andrew Morton
2002-08-01 8:58 ` Jens Axboe
2002-08-01 14:45 ` Steven Cole
2002-08-01 18:57 ` Andrew Morton
2002-08-01 20:15 ` Steven Cole
2002-08-06 3:46 ` Bill Davidsen
2002-08-06 4:30 ` Andrew Morton
2002-08-06 14:07 ` Steven Cole
2002-08-06 14:20 ` Rik van Riel
2002-08-06 17:12 ` Andrew Morton
2002-08-06 5:42 ` Jens Axboe
2002-08-06 8:30 ` Adrian Bunk
2002-08-06 8:48 ` Jens Axboe [this message]
2002-08-06 10:31 ` Lincoln Dale
2002-08-06 12:59 ` Rik van Riel
2002-08-07 1:09 ` Bill Davidsen
2002-08-07 2:54 ` Steven Cole
2002-08-07 22:30 ` Bill Davidsen
2002-08-07 22:39 ` Rik van Riel
2002-08-07 23:44 ` Bill Davidsen
2002-08-07 23:53 ` Rik van Riel
2002-08-09 17:46 ` Bill Davidsen
2002-08-09 19:27 ` Rik van Riel
2002-08-01 7:55 ` Keith Owens
2002-08-01 8:10 ` Jens Axboe
2002-08-04 6:50 ` H. Peter Anvin
2002-08-01 11:32 ` Willy TARREAU
2002-08-01 13:54 ` Alan Cox
2002-08-01 12:48 ` Willy TARREAU
2002-08-01 12:12 ` Linux v2.4.19-rc5 - APM bug Willy TARREAU
2002-08-01 13:32 ` [PANIC] APM bug with -rc4 and -rc5 Willy TARREAU
2002-08-01 14:55 ` Alan Cox
2002-08-01 13:56 ` Willy Tarreau
2002-08-01 15:24 ` Willy Tarreau
2002-08-01 16:53 ` Alan Cox
2002-08-01 16:41 ` Willy Tarreau
2002-08-01 20:35 ` [PATCH] solved APM bug with -rc5 Willy TARREAU
2002-08-01 20:52 ` Richard Gooch
2002-08-01 20:54 ` Richard Gooch
2002-08-01 21:17 ` Willy TARREAU
2002-08-01 22:37 ` Alan Cox
2002-08-01 20:58 ` Dave Jones
2002-08-01 22:16 ` Alan Cox
2002-08-01 21:07 ` Willy Tarreau
2002-08-01 21:47 ` Linus Torvalds
2002-08-02 0:12 ` [PATCH] solved APM bug with -rc5 (take 2) Willy TARREAU
2002-08-02 1:47 ` [PATCH] pdc20265 problem Nick Orlov
2002-08-02 2:29 ` Nick Orlov
2002-08-02 12:27 ` Alan Cox
2002-08-02 12:52 ` Nick Orlov
2002-08-02 14:00 ` Bartlomiej Zolnierkiewicz
2002-08-02 14:45 ` Nick Orlov
-- strict thread matches above, loose matches on Subject: below --
2002-08-06 4:36 Linux v2.4.19-rc5 rwhron
2002-08-07 3:00 ` Bill Davidsen
2002-08-06 20:12 Peter Wong
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=20020806084851.GC1164@suse.de \
--to=axboe@suse.de \
--cc=bunk@fs.tum.de \
--cc=davidsen@tmr.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