From: Mark Lord <liml@rtr.ca>
To: Jeff Garzik <jeff@garzik.org>
Cc: Justin Piszcz <jpiszcz@lucidpixels.com>,
linux-kernel@vger.kernel.org,
IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: Why is NCQ enabled by default by libata? (2.6.20)
Date: Tue, 27 Mar 2007 10:26:59 -0400 [thread overview]
Message-ID: <460929B3.60303@rtr.ca> (raw)
In-Reply-To: <4608B2B9.7090503@garzik.org>
Jeff Garzik wrote:
>
> In some cases, NCQ firmware may be broken. There is a Maxtor firmware
> id, and some Hitachi ids that people are leaning towards recommending be
> added to the libata 'horkage' list.
Western Digital "Raptor" drives (the 10K rpm things) are also somewhat
borked in NCQ mode, depending on the application.
Their firmware turns off all drive readahead during NCQ.
This makes them very good for an email/news server application,
but also causes them to suck for regular desktop applications.
Because of this, they use special software drivers under MSwin
which detect large sequential accesses, and avoid NCQ during such times.
Cheers
-ml
next prev parent reply other threads:[~2007-03-27 14:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0703241232580.11608@p34.internal.lan>
2007-03-27 5:59 ` Why is NCQ enabled by default by libata? (2.6.20) Jeff Garzik
2007-03-27 14:26 ` Mark Lord [this message]
2007-03-27 18:18 ` Mark Rustad
2007-03-27 18:38 ` Jeff Garzik
2007-03-27 22:12 ` Mark Rustad
2007-03-31 12:55 ` Ric Wheeler
2007-03-27 16:16 linux
2007-03-27 16:25 ` Justin Piszcz
2007-03-27 16:41 ` linux
2007-03-27 16:44 ` Justin Piszcz
2007-03-27 16:58 ` linux
2007-03-27 17:03 ` Justin Piszcz
2007-03-28 14:42 ` Phillip Susi
2007-03-28 14:48 ` Jeff Garzik
2007-03-28 15:22 ` Andy Warner
2007-03-29 17:28 ` Phillip Susi
2007-03-29 18:40 ` linux
2007-03-29 18:51 ` Jeff Garzik
2007-03-29 21:35 ` Alan Cox
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=460929B3.60303@rtr.ca \
--to=liml@rtr.ca \
--cc=jeff@garzik.org \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-ide@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).