mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Chris Snook <csnook@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
	xfs@oss.sgi.com
Subject: Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
Date: Wed, 28 May 2008 15:27:58 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.1.10.0805281523560.29755@p34.internal.lan> (raw)
In-Reply-To: <483DB0EC.3090403@redhat.com>



On Wed, 28 May 2008, Chris Snook wrote:

> Justin Piszcz wrote:
>> 
>> 
>> On Wed, 28 May 2008, Chris Snook wrote:
>> 
>>> Justin Piszcz wrote:
>>>> Hardware:
>>>> 
>>> Given that one of the greatest benefits of NCQ/TCQ is with parity RAID, 
>>> I'd be fascinated to see how enabling NCQ changes your results.  Of 
>>> course, you'd want to use a single SATA controller with a known good NCQ 
>>> implementation, and hard drives known to not do stupid things like disable 
>>> readahead when NCQ is enabled.
>> Only/usually on multi-threaded jobs/tasks, yes?
>
> Generally, yes, but there's caching and readahead at various layers in 
> software that can expose the benefit on certain single-threaded workloads as 
> well.
>
>> Also, I turn off NCQ on all of my hosts that has it enabled by default 
>> because
>> there are many bugs that occur when NCQ is on, they are working on it in 
>> the
>> libata layer but IMO it is not safe at all for running SATA disks w/NCQ as
>> with it on I have seen drives drop out of the array (with it off, no 
>> problems).
>> 
>
> Are you using SATA drives with RAID-optimized firmware?  Most SATA 
> manufacturers have variants of their drives for a few dollars more that have 
> firmware that provides bounded latency for error recovery operations, for 
> precisely this reason.
I see--however, as I understood it there were bugs utilizing NCQ in libata?

But FYI--
In this test, they were regular SATA drives, not special raid-ones (RE2,etc).

Thanks for the info!

Justin.


  reply	other threads:[~2008-05-28 19:28 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-28  8:53 Justin Piszcz
2008-05-28 10:54 ` Peter Rabbitson
2008-05-28 11:05   ` Justin Piszcz
2008-05-28 15:40 ` Chris Snook
2008-05-28 17:32   ` Justin Piszcz
2008-05-28 17:53     ` Justin Piszcz
2008-05-28 19:22     ` Chris Snook
2008-05-28 19:27       ` Justin Piszcz [this message]
2008-05-29  9:57         ` Kasper Sandberg
2008-05-29 21:08           ` Justin Piszcz
2008-05-28 16:34 ` Jens Bäckman
2008-05-28 16:40   ` Chris Snook
2008-05-28 16:46   ` Bryan Mesich
2008-05-28 17:33   ` Justin Piszcz
2008-05-28 18:57   ` Alan Cox
2008-05-28 23:00     ` Bill Davidsen
2008-05-29 11:22       ` Alan Cox
2008-05-30 12:22         ` Bill Davidsen
2008-05-28 19:02 ` Keld Jørn Simonsen
2008-05-28 19:05   ` Justin Piszcz
2008-05-28 23:09 ` Bill Davidsen
2008-05-29  6:37   ` Michal Soltys
2008-05-29  6:44 ` Holger Kiehl
2008-05-29 12:06   ` Justin Piszcz
2008-05-29 17:02   ` Justin Piszcz
2008-05-30 12:55     ` Bill Davidsen
2008-05-30 14:23       ` Keld Jørn Simonsen

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=alpine.DEB.1.10.0805281523560.29755@p34.internal.lan \
    --to=jpiszcz@lucidpixels.com \
    --cc=csnook@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=xfs@oss.sgi.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

all inboxes | Powered by JetHome®