From: Andreas Dilger <adilger@turbolabs.com>
To: linux-kernel@vger.kernel.org
Cc: S.Akhtary@TeraPort.de, mjustice@boxxtech.com
Subject: Re: Tuning Linux for high-speed disk subsystems
Date: Thu, 22 Nov 2001 09:30:32 -0700 [thread overview]
Message-ID: <20011122093032.H1308@lynx.no> (raw)
In-Reply-To: <3BFCD029.DAED8BF7@TeraPort.de>
In-Reply-To: <3BFCD029.DAED8BF7@TeraPort.de>; from Martin.Knoblauch@TeraPort.de on Thu, Nov 22, 2001 at 11:15:05AM +0100
> Re: Tuning Linux for high-speed disk subsystems
> > As I count your disks may be the double for the best case. I read here on
> > LKML a post that someone claims that W2k deliever 250 MB/s with such a
> > configuration. Linux 2.4 should do the same. Ask the SCSI gurus.
>
> That may have been my post you refer to. With 2x5 disks, each capable of
> 50 MB/s by itself, we can stream 255 MB/s very smoothly in either direction
> with W2K --- as long as FILE_FLAG_NOBUFFER is used. With standard
> reads the number is more like 100 MB/s if I recall correctly, so the buffer
> cache can definitely get in the way.
>
> With Linux + XFS I was getting 250 MB/s read and 220 MB/s write (with a
> bit less smoothness than W2K) using O_DIRECT and no high mem to avoid
> bounce buffer copies. Using standard reads the numbers drop to around
> 120 MB/s. That was a couple of weeks ago and I want to try tweaking some
> more but a co-worker has "borrowed" pieces of the hardware for the moment.
Jusy FYI, Linus announced that he had returned Andrea's O_DIRECT support
to the most recent 2.4.15-pre kernel, so you are no longer restricted to
using XFS for no-cache I/O. Whether you will be able to beat XFS for
speed using any other filesystem is another question.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2001-11-22 16:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-22 10:15 Tuning Linux for high-speed disk subsystems Martin Knoblauch
2001-11-22 16:30 ` Andreas Dilger [this message]
[not found] <3B6867E6CB09B24385A73719A50C7C9A79791F@athena.boxxtech.com>
2001-11-16 16:53 ` Marvin Justice
-- strict thread matches above, loose matches on Subject: below --
2001-11-16 2:56 Dieter Nützel
2001-11-16 11:51 ` Roy Sigurd Karlsbakk
2001-11-16 15:24 ` Dieter Nützel
2001-11-13 20:38 Torrey Hoffman
2001-11-13 15:58 Jesse Pollard
2001-11-13 14:29 Roy Sigurd Karlsbakk
2001-11-13 16:43 ` Ragnar Kjørstad
2001-11-13 16:51 ` Alan Cox
2001-11-13 17:59 ` Craig I. Hagan
2001-11-13 16:18 ` Marcelo Tosatti
2001-11-14 10:33 ` Roy Sigurd Karlsbakk
2001-11-14 10:35 ` Roy Sigurd Karlsbakk
2001-11-13 20:00 ` Dan Hollis
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=20011122093032.H1308@lynx.no \
--to=adilger@turbolabs.com \
--cc=S.Akhtary@TeraPort.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mjustice@boxxtech.com \
/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