From: Andrew Morton <akpm@osdl.org>
To: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
Cc: linux-kernel@vger.kernel.org, axboe@suse.de
Subject: Re: Direct io on block device has performance regression on 2.6.x kernel
Date: Tue, 8 Mar 2005 22:27:37 -0800 [thread overview]
Message-ID: <20050308222737.3712611b.akpm@osdl.org> (raw)
In-Reply-To: <200503090139.j291dfg16356@unix-os.sc.intel.com>
"Chen, Kenneth W" <kenneth.w.chen@intel.com> wrote:
>
> Direct I/O on block device running 2.6.X kernel is a lot SLOWER
> than running on a 2.4 Kernel!
>
A little bit slower, it appears. It used to be faster.
> ...
>
> synchronous I/O AIO
> (pread/pwrite/read/write) io_submit
> 2.4.21 based
> (RHEL3) 265,122 229,810
>
> 2.6.9 218,565 206,917
> 2.6.10 213,041 205,891
> 2.6.11 212,284 201,124
What sort of CPU?
What speed CPU?
What size requests?
Reads or writes?
At 5 usecs per request I figure that's 3% CPU utilisation for 16k requests
at 100 MB/sec.
Once you bolt this onto a real device driver the proportional difference
will fall, due to addition of the constant factor.
Once you bolt all this onto a real disk controller all the numbers will get
worse (but in a strictly proportional manner) due to the disk transfers
depriving the CPU of memory bandwidth.
The raw driver is deprecated and we'd like to remove it. The preferred way
of doing direct-IO against a blockdev is by opening it with O_DIRECT.
Your patches don't address blockdevs opened with O_DIRECT. What you should
do is to make def_blk_aops.direct_IO point at a new function. That will
then work correctly with both raw and with open(/dev/hdX, O_DIRECT).
But before doing anything else, please bench this on real hardware, see if
it is worth pursuing. And gather an oprofile trace of the existing code.
next prev parent reply other threads:[~2005-03-09 6:30 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 1:39 Direct io on block device has performance regression on 2.6.x kernel Chen, Kenneth W
2005-03-09 6:27 ` Andrew Morton [this message]
2005-03-09 17:21 ` Chen, Kenneth W
2005-03-09 20:04 ` Andrew Morton
2005-03-09 21:59 ` Chen, Kenneth W
2005-03-09 22:44 ` Andrew Morton
2005-03-10 1:11 ` Chen, Kenneth W
2005-03-10 1:33 ` Andrew Morton
2005-03-10 1:44 ` Chen, Kenneth W
2005-03-10 2:25 ` Andrew Morton
2005-03-10 3:47 ` Chen, Kenneth W
2005-03-10 4:04 ` David Lang
2005-03-10 4:10 ` Andrew Morton
2005-03-10 4:15 ` Direct io on block device has performance regression on 2.6.xkernel David Lang
2005-03-10 4:09 ` Direct io on block device has performance regression on 2.6.x kernel Andrew Morton
2005-03-10 18:31 ` Chen, Kenneth W
2005-03-10 20:30 ` Andrew Morton
2005-03-10 21:42 ` Chen, Kenneth W
2005-03-10 22:01 ` Andrew Morton
2005-03-10 4:28 ` Andrew Vasquez
-- strict thread matches above, loose matches on Subject: below --
2005-03-09 1:53 Chen, Kenneth W
2005-03-09 22:18 Chen, Kenneth W
2005-03-09 23:23 ` Andi Kleen
2005-03-09 23:52 ` Jesse Barnes
2005-03-09 23:52 ` Jesse Barnes
2005-03-10 1:00 ` Chen, Kenneth W
2005-03-10 0:57 ` Chen, Kenneth W
2005-03-10 1:24 Chen, Kenneth W
2005-03-10 2:04 Chen, Kenneth W
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=20050308222737.3712611b.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=axboe@suse.de \
--cc=kenneth.w.chen@intel.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