linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Majed B." <majedb@gmail.com>
To: linux-raid@vger.kernel.org
Subject: Re: Spurious HD convictions
Date: Tue, 15 Dec 2009 11:47:04 +0300	[thread overview]
Message-ID: <70ed7c3e0912150047v1d3284dbk35282f8916d0ba4f@mail.gmail.com> (raw)
In-Reply-To: <4b271970.5e44f10a.484f.ffffdd07SMTPIN_ADDED@mx.google.com>

As far as I know, the numbers in between define the queue depth of
commands sent to the disks.

It's a matter of whether you want the disk(s) firmware to manage
sorting & executing the commands (when the queue is > 1) or not. In
all cases, as far as I know, the kernel does the sorting before
sending the commands to the disk(s). So if you notice better
performance (when the array is stable) with the queue=1, then keep it
that way.

On Tue, Dec 15, 2009 at 8:06 AM, Leslie Rhorer <lrhorer@satx.rr.com> wrote:
>> Hi Leslie,
>>
>> I was wondering if you were able to stop the weird behavior with your
>> disks.
>
>        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?
>
>



-- 
       Majed B.
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2009-12-15  8:47 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. [this message]
2009-12-16  5:40       ` Leslie Rhorer
2009-12-16  5:41   ` Leslie Rhorer
2009-12-16  9:13     ` Robin Hill
  -- 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=70ed7c3e0912150047v1d3284dbk35282f8916d0ba4f@mail.gmail.com \
    --to=majedb@gmail.com \
    --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).