From: Tejun Heo <htejun@gmail.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: Some NCQ numbers...
Date: Wed, 04 Jul 2007 10:19:55 +0900 [thread overview]
Message-ID: <468AF5BB.10005@gmail.com> (raw)
In-Reply-To: <468AB1A7.9010201@msgid.tls.msk.ru>
Hello,
Michael Tokarev wrote:
> Well. It looks like the results does not depend on the
> elevator. Originally I tried with deadline, and just
> re-ran the test with noop (hence the long delay with
> the answer) - changing linux elevator changes almost
> nothing in the results - modulo some random "fluctuations".
I see. Thanks for testing.
> In any case, NCQ - at least in this drive - just does
> not work. Linux with its I/O elevator may help to
> speed things up a bit, but the disk does nothing in
> this area. NCQ doesn't slow things down either - it
> just does not work.
>
> The same's for ST3250620NS "enterprise" drives.
>
> By the way, Seagate announced Barracuda ES 2 series
> (in range 500..1200Gb if memory serves) - maybe with
> those, NCQ will work better?
No one would know without testing.
> Or maybe it's libata which does not implement NCQ
> "properly"? (As I shown before, with almost all
> ol'good SCSI drives TCQ helps alot - up to 2x the
> difference and more - with multiple I/O threads)
Well, what the driver does is minimal. It just passes through all the
commands to the harddrive. After all, NCQ/TCQ gives the harddrive more
responsibility regarding request scheduling.
--
tejun
next prev parent reply other threads:[~2007-07-04 1:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-28 10:51 Some NCQ numbers Michael Tokarev
2007-06-28 11:01 ` Michael Tokarev
2007-07-03 8:19 ` Tejun Heo
2007-07-03 20:29 ` Michael Tokarev
2007-07-04 1:19 ` Tejun Heo [this message]
2007-07-04 9:43 ` Michael Tokarev
2007-07-04 10:22 ` Justin Piszcz
2007-07-04 10:33 ` Justin Piszcz
2007-07-05 19:00 ` Bill Davidsen
2007-07-09 11:07 ` Justin Piszcz
2007-07-09 12:26 ` Jens Axboe
2007-07-05 19:22 ` Bill Davidsen
2007-07-04 14:40 ` James Bottomley
2007-07-09 12:26 ` Jens Axboe
2007-07-04 15:44 ` Dan Aloni
2007-07-04 16:17 ` Michael Tokarev
2007-07-04 16:44 ` Dan Aloni
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=468AF5BB.10005@gmail.com \
--to=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mjt@tls.msk.ru \
/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).