From: Jeff Garzik <jeff@garzik.org>
To: linux-ide@vger.kernel.org, crane.cai@amd.com, Henry.Su@amd.com,
shane.huang@amd.com
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFC] ahci: fix SB600 h/w errata issue
Date: Wed, 05 Mar 2008 07:49:03 -0500 [thread overview]
Message-ID: <47CE96BF.50108@garzik.org> (raw)
In-Reply-To: <20080228204348.GA30539@havoc.gtf.org>
Jeff Garzik wrote:
> I haven't seen anyone work on the recent SB600 errata, where the
> hardware does not like 256-length PRD entries.
>
> Is this correct, AMD folks?
>
> It hurts performance on SB600, but it is more important to get a
> correct patch eliminating the data corruption/lockups, and then later
> on tune for performance.
>
> We simply limit each command to a maximum of 255 sectors, on SB600.
>
> Signed-off-by: Jeff Garzik <jgarzik@redhat.com>
> ---
> drivers/ata/ahci.c | 14 +++++++++++++-
> 1 file changed, 13 insertions(+), 1 deletion(-)
Based on Henry's response, I'm going to assume AMD approves of this patch...
prev parent reply other threads:[~2008-03-05 12:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 20:43 [PATCH RFC] ahci: fix SB600 h/w errata issue Jeff Garzik
2008-03-05 2:15 ` Su, Henry
2008-03-05 12:49 ` Jeff Garzik [this message]
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=47CE96BF.50108@garzik.org \
--to=jeff@garzik.org \
--cc=Henry.Su@amd.com \
--cc=crane.cai@amd.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shane.huang@amd.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).