From: Robin Hill <robin@robinhill.me.uk>
To: linux-raid@vger.kernel.org
Subject: Re: Spurious HD convictions
Date: Wed, 16 Dec 2009 09:13:31 +0000 [thread overview]
Message-ID: <20091216091331.GA15689@cthulhu.home.robinhill.me.uk> (raw)
In-Reply-To: <FD.42.04641.7F2782B4@cdptpa-omtalb.mail.rr.com>
[-- Attachment #1: Type: text/plain, Size: 1190 bytes --]
On Tue Dec 15, 2009 at 11:41:03PM -0600, Leslie Rhorer wrote:
> It seems to have done so, yes. I've looked around the web trying to
> find some additional info, but I've come up empty handed. Perhaps someone
> here can answer at least one of my questions? I know that putting a value
> of 32 into /sys/block/<driveID>/device/queue_depth fully enables NCQ, and
> putting a value of 1 there disables NCQ. What do all the numbers in between
> do?
>
I believe the value sets the allowed queue length. A value of 1 thus
effectively disables queueing. Most ATA drives have a maximum queue
depth of 32 so this is usually set for fully enabling it (though I
believe it's recommended only to use 31 - this seems to be the default).
If you set it to 32 and the drive has a shorter maximum queue, the
kernel will use the drive's maximum instead.
Setting any value is permitted, there's just generally little point in
doing so.
Cheers,
Robin
--
___
( ' } | Robin Hill <robin@robinhill.me.uk> |
/ / ) | Little Jim says .... |
// !! | "He fallen in de water !!" |
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-12-16 9:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-13 3:44 Spurious HD convictions lrhorer
2009-12-14 20:06 ` Majed B.
[not found] ` <4b271970.5e44f10a.484f.ffffdd07SMTPIN_ADDED@mx.google.com>
2009-12-15 8:47 ` Majed B.
2009-12-16 5:40 ` Leslie Rhorer
2009-12-16 5:41 ` Leslie Rhorer
2009-12-16 9:13 ` Robin Hill [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-12-13 2:07 lrhorer
2009-12-13 2:02 lrhorer
2009-12-13 2:57 ` Majed B.
2009-12-12 19:42 Leslie Rhorer
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=20091216091331.GA15689@cthulhu.home.robinhill.me.uk \
--to=robin@robinhill.me.uk \
--cc=linux-raid@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).