From: Maurice Hilarius <maurice@harddata.com>
To: Wil Reichert <wil.reichert@gmail.com>
Cc: tfjellstrom@shaw.ca, linux-raid@vger.kernel.org
Subject: Re: Awful RAID5 random read performance
Date: Tue, 02 Jun 2009 09:14:39 -0600 [thread overview]
Message-ID: <4A2541DF.40505@harddata.com> (raw)
In-Reply-To: <7a329d910906020757vec0de52xb6b7e4557e82c489@mail.gmail.com>
Wil Reichert wrote:
> On Mon, Jun 1, 2009 at 5:43 AM, Maurice Hilarius <maurice@harddata.com> wrote:
>
>> Thomas Fjellstrom wrote:
>>
>>> ..
>>> Yet I've heard NCQ makes some things worse. Some raid tweaking pages tell
>>> you to try disabling NCQ.
>>>
>>>
>> Not so relevant here.
>> This recommendation to disable drive NCQ is generally due tot he fact that
>> NCQ implementations by various manufacturers tend
>> to differ in behaviour, and, in some cases , is just plain "broken".
>>
>
> Not trying to start a flamewar on whos hardware is better, but I'd
> love to get clarification on that last statement. I've always been
> under the impression Intel gets their NCQ right (works for me). All
> the reviews I've read on the current set of AMD southbridges indicate
> they don't but I've no personal experience there. No idea about
> nvidia or the cheap add-in sata cards like Silicon Image.
>
> Wil
>
From speaking with hardware RAID card manufacturers support engineers
over the past few years,
there have been several instances where NCQ implementations were
incomplete, or faulty, or both.
This seems to have improved a lot over the last year or two, so I think
it is likely now "OK".
However, from the earlier history I think there is a tendency for
people now to assume it is "broken",
and to turn it off.
--
Regards, Maurice
next prev parent reply other threads:[~2009-06-02 15:14 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-30 21:46 Awful RAID5 random read performance Maurice Hilarius
2009-05-31 6:25 ` Michael Tokarev
2009-05-31 7:47 ` Thomas Fjellstrom
2009-05-31 12:29 ` John Robinson
2009-05-31 15:41 ` Leslie Rhorer
2009-05-31 16:56 ` Thomas Fjellstrom
2009-05-31 18:26 ` Keld Jørn Simonsen
2009-06-02 18:54 ` Bill Davidsen
2009-06-02 19:47 ` Keld Jørn Simonsen
2009-06-02 23:13 ` John Robinson
2009-06-03 18:38 ` Bill Davidsen
2009-06-03 19:57 ` John Robinson
2009-06-03 22:21 ` Goswin von Brederlow
2009-06-04 11:23 ` Keld Jørn Simonsen
2009-06-04 22:40 ` Nifty Fedora Mitch
2009-06-06 23:06 ` Bill Davidsen
2009-06-01 1:19 ` Carlos Carvalho
2009-06-01 4:57 ` Leslie Rhorer
2009-06-01 5:39 ` Thomas Fjellstrom
2009-06-01 12:43 ` Maurice Hilarius
2009-06-02 14:57 ` Wil Reichert
2009-06-02 15:14 ` Maurice Hilarius [this message]
2009-06-02 19:47 ` Bill Davidsen
2009-06-01 11:41 ` Goswin von Brederlow
2009-06-03 1:57 ` Leslie Rhorer
2009-05-31 17:19 ` Goswin von Brederlow
2009-06-01 12:01 ` John Robinson
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=4A2541DF.40505@harddata.com \
--to=maurice@harddata.com \
--cc=linux-raid@vger.kernel.org \
--cc=tfjellstrom@shaw.ca \
--cc=wil.reichert@gmail.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;
as well as URLs for NNTP newsgroup(s).