From: Jeff Garzik <jeff@garzik.org>
To: peer chen <peerchen@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
linux-ide <linux-ide@vger.kernel.org>,
akpm <akpm@linux-foundation.org>, Kuan Luo <kluo@nvidia.com>
Subject: Re: [PATCH] sata_nv,ahci: add the ahci legacy mode support to sata_nv
Date: Thu, 18 Oct 2007 22:56:33 -0400 [thread overview]
Message-ID: <47181CE1.4000802@garzik.org> (raw)
In-Reply-To: <cfaab6210710160108x1328086cse991f668e23e569e@mail.gmail.com>
peer chen wrote:
> I hope one of the following patches can be merged to 2.6.24.
> ==========================
> http://lkml.org/lkml/2007/10/8/93
> http://lkml.org/lkml/2007/9/25/20
Unfortunately I do not feel like this is the right course of action.
Experience from Intel platforms tells us that our users get very unhappy
when their silicon supports AHCI mode, but they are forced into using a
less-performant mode. A popular example is an <unnamed> OEM whose BIOS
had no method whatsoever for enabling AHCI -- didn't even program the
PCI BAR -- even though tests showed the AHCI mode worked just fine when
manually programmed.
AHCI is more likely to provide a /stable/ Serial ATA experience, because
the silicon deals primarily with sending and receiving FIS's, and not
much else. In constrast, experience has shown the legacy IDE interface
to be a less reliable method of SATA support. And certainly AHCI is
much, much faster with less per-command overhead.
Given that AHCI is both faster and more stable, I feel it is the best
policy to enable AHCI when the hardware supports it, regardless of PCI
class code (IDE, SATA, or RAID).
> Yes, I agree to set the 'swncq' as default for 2.6.24, after all, for
> our server customers, stability is far more important than the new
> feature no matter the problem is caused by drive or controller.
Agreed. Done!
Jeff
next prev parent reply other threads:[~2007-10-19 2:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 5:23 [PATCH] sata_nv,ahci: add the ahci legacy mode support to sata_nv Peer Chen
2007-09-25 7:08 ` Jeff Garzik
2007-09-25 7:52 ` Peer Chen
2007-09-25 8:13 ` Jeff Garzik
2007-09-25 9:08 ` Peer Chen
2007-10-12 21:17 ` Jeff Garzik
2007-10-16 8:08 ` peer chen
2007-10-19 2:56 ` Jeff Garzik [this message]
2007-10-19 6:58 ` peer chen
2007-10-19 7:25 ` Jeff Garzik
2007-10-22 1:55 ` peer chen
2007-11-10 4:04 ` Jeff Garzik
2007-11-10 5:00 ` Jeff Garzik
2007-11-10 19:00 ` Robert Hancock
2007-12-11 12:04 ` [PATCH] sata_nv,adma: fix error when rmmod sata_nv Kuan Luo
2007-12-12 8:18 ` Tejun Heo
2007-12-13 3:10 ` Kuan Luo
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=47181CE1.4000802@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=kluo@nvidia.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peerchen@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