All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phillip Susi <psusi@cfl.rr.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux@horizon.com, htejun@gmail.com, jeff@garzik.org,
	linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Why is NCQ enabled by default by libata? (2.6.20)
Date: Wed, 28 Mar 2007 10:42:47 -0400	[thread overview]
Message-ID: <460A7EE7.5070101@cfl.rr.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0703271224400.5965@p34.internal.lan>

Justin Piszcz wrote:
> I would try with write-caching enabled.
> Also, the RAID5/RAID10 you mention seems like each volume is on part of
> the platter, a strange setup you got there :)

Shouldn't NCQ only help write performance if write caching is 
_disabled_?  Since write cache essentially is just non tagged command 
queuing?

  parent reply	other threads:[~2007-03-28 14:42 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-27 16:16 Why is NCQ enabled by default by libata? (2.6.20) 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 [this message]
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
2007-03-29 21:47         ` David Schwartz
2007-03-30 16:33           ` Lennart Sorensen
     [not found] <fa.NmF2xJwO4BeVbJrFRkf7oV9EYmQ@ifi.uio.no>
     [not found] ` <fa.39luedDWsoqip+QMNtfAv8jvyNg@ifi.uio.no>
     [not found]   ` <fa.b1cZfpMNhZ0teK/UauKLDWw60Jc@ifi.uio.no>
     [not found]     ` <fa.xWaBy6HZTRTgI+PxinV8ajuOlJI@ifi.uio.no>
     [not found]       ` <fa.BiSx71HKysC9QIpS8DLip5BmfxI@ifi.uio.no>
2007-04-01 17:28         ` Robert Hancock
     [not found] <fa.MhN9pBMjZID4rnTNn+fU01uZiss@ifi.uio.no>
2007-03-24 22:11 ` Robert Hancock
  -- strict thread matches above, loose matches on Subject: below --
2007-03-24 16:38 Justin Piszcz
2007-03-24 18:43 ` Alan Cox
2007-03-27  9:55   ` Justin Piszcz
2007-03-27 10:10     ` Tejun Heo
2007-03-27 10:30       ` Justin Piszcz
2007-03-27  5:59 ` 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

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=460A7EE7.5070101@cfl.rr.com \
    --to=psusi@cfl.rr.com \
    --cc=htejun@gmail.com \
    --cc=jeff@garzik.org \
    --cc=jpiszcz@lucidpixels.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@horizon.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.