From: Andrew Morton <akpm@digeo.com>
To: Lincoln Dale <ltd@cisco.com>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Chuck Lever <cel@citi.umich.edu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux NFS List <nfs@lists.sourceforge.net>
Subject: Re: [PATCH] direct-IO API change
Date: Sat, 05 Oct 2002 12:34:04 -0700 [thread overview]
Message-ID: <3D9F3EAC.590738BA@digeo.com> (raw)
In-Reply-To: 5.1.0.14.2.20021005194507.031018c0@mira-sjcm-3.cisco.com
Lincoln Dale wrote:
>
> At 04:23 PM 4/10/2002 -0700, Linus Torvalds wrote:
> >Especially since I thought that O_DIRECT on the regular file (or block
> >device) performed about as well as raw does anyway these days? Or is that
> >just one of my LSD-induced flashbacks?
>
> from my multiple 64/66 PCI bus + multiple 2gbit/s FC HBA tests, yes,
> they're around the same.
> (now up to 390mbyte/sec throughput on latest & greatest x86 hardware i
> have; front-side-bus no longer the limiting factor, but dual 64/66 PCI).
>
> of course, purely synthetic tests designed to stress Fibre Channel
> switching infrastructure, not real-world disk i/o..
>
direct-io has lost its challenge ;)
I'd love to see the result of some pagecache testing on that
setup if you have time.
Nothing fancy - just:
for i in $(each ext2 mountpoint)
do
dd if=/dev/zero of=$i/foo bs-1M count=4000 &
done
vmstat 1
and
for i in $(each ext2 mountpoint)
do
cat $i/foo > /dev/null &
done
vmstat 1
Linus's current BK tree has a few warmups which will help the
writeout phase a little.
prev parent reply other threads:[~2002-10-05 19:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-04 22:10 [PATCH] direct-IO API change Chuck Lever
2002-10-04 22:25 ` Linus Torvalds
2002-10-04 22:37 ` Andrew Morton
2002-10-04 23:23 ` Linus Torvalds
2002-10-04 23:35 ` Andrew Morton
2002-10-04 23:44 ` Linus Torvalds
2002-10-04 23:56 ` Badari Pulavarty
2002-10-05 0:11 ` Linus Torvalds
2002-10-08 13:33 ` Terje Eggestad
[not found] ` <Pine.LNX.4.44.0210041621170.2526-100000@home.transmeta.com >
2002-10-05 9:49 ` Lincoln Dale
2002-10-05 19:34 ` Andrew Morton [this message]
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=3D9F3EAC.590738BA@digeo.com \
--to=akpm@digeo.com \
--cc=cel@citi.umich.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=ltd@cisco.com \
--cc=nfs@lists.sourceforge.net \
--cc=torvalds@transmeta.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;
as well as URLs for NNTP newsgroup(s).