From: Jens Axboe <jens.axboe@oracle.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: jeff@garzik.org
Subject: Re: ahci: work around ATI SB600 h/w quirk
Date: Thu, 6 Mar 2008 09:18:23 +0100 [thread overview]
Message-ID: <20080306081822.GO6704@kernel.dk> (raw)
In-Reply-To: <200803060259.m262x3tp008780@hera.kernel.org>
On Thu, Mar 06 2008, Linux Kernel Mailing List wrote:
> Gitweb: http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=a878539ef994787c447a98c2e3ba0fe3dad984ec
> Commit: a878539ef994787c447a98c2e3ba0fe3dad984ec
> Parent: 6ddd68615ae9b21096545d7d6ab0f04113ae8b42
> Author: Jeff Garzik <jeff@garzik.org>
> AuthorDate: Thu Feb 28 15:43:48 2008 -0500
> Committer: Jeff Garzik <jeff@garzik.org>
> CommitDate: Wed Mar 5 07:53:06 2008 -0500
>
> ahci: work around ATI SB600 h/w quirk
>
> This addresses the recent ATI SB600 errata, where the hardware does
> not like 256-length PRD entries during FPDMA (aka NCQ).
>
> 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.
Why not limit it to 255 segments, if that's the real issue?
--
Jens Axboe
parent reply other threads:[~2008-03-06 8:18 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <200803060259.m262x3tp008780@hera.kernel.org>]
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=20080306081822.GO6704@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
/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