public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Lord <lkml@rtr.ca>
To: Phillip Susi <psusi@cfl.rr.com>
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: Wed, 04 Apr 2007 11:36:50 -0400	[thread overview]
Message-ID: <4613C612.5040600@rtr.ca> (raw)
In-Reply-To: <4612A854.1070702@cfl.rr.com>

Phillip Susi wrote:
> Mark Lord wrote:
>> But WD drives, in particular the Raptor series, have a firmware "feature"
>> that disables "drive readahead" whenever NCQ is in use.
> 
> Why is this an issue?  Shouldn't the kernel be sending down its own 
> readahead requests to keep the disk busy?

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.

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.

-ml

  reply	other threads:[~2007-04-04 15:36 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 [this message]
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=4613C612.5040600@rtr.ca \
    --to=lkml@rtr.ca \
    --cc=csnook@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paapaa125@hotmail.com \
    --cc=psusi@cfl.rr.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