From: Phillip Susi <psusi@cfl.rr.com>
To: Mark Lord <lkml@rtr.ca>
Cc: Chris Snook <csnook@redhat.com>, Paa Paa <paapaa125@hotmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: Lower HD transfer rate with NCQ enabled?
Date: Thu, 05 Apr 2007 11:30:18 -0400 [thread overview]
Message-ID: <4615160A.4090506@cfl.rr.com> (raw)
In-Reply-To: <4613C612.5040600@rtr.ca>
Mark Lord wrote:
> The drive firmware readahead is inherently *way* more effective than
> other forms, and without it, sequential read performance really suffers.
> Regardless of how software tries to compensate.
Why? As the platter spins under the head, the drive can either read or
ignore the data. As long as it keeps reading the track, it can't go any
faster. Whether in response to its own readahead or to the request
queue from the host, either way it should read the data. If its own
readahead is faster, then either the host must not be properly
performing readahead and keeping the drive request queue filled with
sequential requests, or the drive firmware must be broken and decides to
ignore the data as it passes under the head, and instead go back to pick
it up on the next rotation.
> This is mostly a problem with the WD Raptor drive, and some other WD
> drives.
> I have not yet encountered/noticed the problem with other brands.
Sounds like this is a serious bug in the WD firmware.
next prev parent reply other threads:[~2007-04-05 15:30 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
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 [this message]
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=4615160A.4090506@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=csnook@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
--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