From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Paa Paa <paapaa125@hotmail.com>
Cc: linux-kernel@vger.kernel.org, Jens Axboe <axboe@kernel.dk>
Subject: Re: Lower HD transfer rate with NCQ enabled?
Date: Wed, 04 Apr 2007 12:06:40 +1000 [thread overview]
Message-ID: <46130830.7040307@yahoo.com.au> (raw)
In-Reply-To: <BAY20-F2534ADD292CC02D5ACAFBCF9670@phx.gbl>
Paa Paa wrote:
>>> Q: What conclusion can I make on "hdparm -t" results or can I make
>>> any conclusions? Do I really have lower performance with NCQ or not?
>>> If I do, is this because of my HD or because of kernel?
>>
>>
>> What IO scheduler are you using? If AS or CFQ, could you try with
>> deadline?
>
>
> I was using CFQ. I now tried with Deadline and that doesn't seem to
> degrade the performance at all! With Deadline I got 60MB/s both with and
> without NCQ. This was with "hdparm -t".
>
> So what does this tell us?
Thanks. I believe CFQ contains some code to keep NCQ depths managable,
which might be causing the problem. I've cc'ed the CFQ author (Jens)
who might be able to give some more ideas.
Thanks for reporting!
--
SUSE Labs, Novell Inc.
next prev parent reply other threads:[~2007-04-04 2:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-03 7:11 Lower HD transfer rate with NCQ enabled? Paa Paa
2007-04-03 9:18 ` Nick Piggin
2007-04-03 21:31 ` Paa Paa
2007-04-04 2:06 ` Nick Piggin [this message]
2007-04-06 21:33 ` Bill Davidsen
2007-04-03 16:31 ` Chris Snook
2007-04-03 16:47 ` Mark Lord
2007-04-03 19:17 ` Phillip Susi
2007-04-04 15:36 ` Mark Lord
2007-04-05 15:30 ` Phillip Susi
2007-04-05 16:11 ` Mark Lord
2007-04-05 16:45 ` Lennart Sorensen
2007-04-09 14:46 ` Phillip Susi
2007-04-10 3:58 ` Mark Lord
-- strict thread matches above, loose matches on Subject: below --
2007-04-05 16:26 Paa Paa
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=46130830.7040307@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=paapaa125@hotmail.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