From: Ric Wheeler <ric@emc.com>
To: Mark Rustad <mrustad@gmail.com>
Cc: Jeff Garzik <jeff@garzik.org>,
Justin Piszcz <jpiszcz@lucidpixels.com>,
linux-kernel@vger.kernel.org,
IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: Why is NCQ enabled by default by libata? (2.6.20)
Date: Sat, 31 Mar 2007 08:55:45 -0400 [thread overview]
Message-ID: <460E5A51.7010601@emc.com> (raw)
In-Reply-To: <711F1620-F483-4CC2-83D6-F2DD577AB5BB@gmail.com>
Mark Rustad wrote:
> On Mar 27, 2007, at 1:38 PM, Jeff Garzik wrote:
>
>> Mark Rustad wrote:
>>> reorder any queued operations. Of course if you really care about
>>> your data, you don't really want to turn write cache on.
>>
>> That's a gross exaggeration. FLUSH CACHE and FUA both ensure data
>> integrity as well.
>>
>> Turning write cache off has always been a performance-killing action
>> on ATA.
>
> Perhaps. Folks I work with would disagree with that, but I am not
> enough of a storage expert to judge. My statement mirrors the
> judgement of folks I work with that know more than I do.
You can easily demonstrate that disabling write cache on a S-ATA or ATA
drive will drop your large file write performance by 50% - just try
writing 10MB files to disk.
ric
next prev parent reply other threads:[~2007-03-31 12:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0703241232580.11608@p34.internal.lan>
2007-03-27 5:59 ` Why is NCQ enabled by default by libata? (2.6.20) Jeff Garzik
2007-03-27 14:26 ` Mark Lord
2007-03-27 18:18 ` Mark Rustad
2007-03-27 18:38 ` Jeff Garzik
2007-03-27 22:12 ` Mark Rustad
2007-03-31 12:55 ` Ric Wheeler [this message]
2007-03-27 16:16 linux
2007-03-27 16:25 ` Justin Piszcz
2007-03-27 16:41 ` linux
2007-03-27 16:44 ` Justin Piszcz
2007-03-27 16:58 ` linux
2007-03-27 17:03 ` Justin Piszcz
2007-03-28 14:42 ` Phillip Susi
2007-03-28 14:48 ` Jeff Garzik
2007-03-28 15:22 ` Andy Warner
2007-03-29 17:28 ` Phillip Susi
2007-03-29 18:40 ` linux
2007-03-29 18:51 ` Jeff Garzik
2007-03-29 21:35 ` Alan Cox
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=460E5A51.7010601@emc.com \
--to=ric@emc.com \
--cc=jeff@garzik.org \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mrustad@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).