linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Kyle McMartin <kyle@canonical.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-ide@vger.kernel.org
Subject: Re: [PATCH] libata: HPA support
Date: Fri, 13 Apr 2007 12:46:37 -0400	[thread overview]
Message-ID: <461FB3ED.50708@pobox.com> (raw)
In-Reply-To: <20070413163341.GA27674@athena.road.mcmartin.ca>

Kyle McMartin wrote:
> On Fri, Apr 13, 2007 at 12:24:34PM -0400, Jeff Garzik wrote:
>> Kyle McMartin wrote:
>>> Oddly, the command at least executes and doesn't MCE (but it's not at all
>>> happy either) if I use ATA_PROT_PIO. I wonder if ATA_PROT_NODATA is 
>>> buggered
>>> on this sata_nv chip (Asus A8N-E).
>>>
>>> Weird...
>>
>> Try turning off ADMA using the module parameter, and see if 
>> ATA_PROT_NODATA magically works.
>>
>> ADMA is an advanced command execution mode, and it may not be 
>> appropriate for certain non-data commands.
>>
> 
> Thanks so much, Jeff! This did it. Think we should drop ADMA by default?
> Do you know off-hand if there's any other drivers this might bite us on?

There is a myriad of choices.  A lot of controllers snoop the ATA 
command set, and perform some special internal behavior (like 
autodetecting taskfile protocol, for example).  Similar to how several 
Promise controllers only use DMA for specific SCSI READ/WRITE commands, 
and PIO for everything else, the most optimal choice is generally to use 
the DMA engine for fast path DMA data commands, and other commands.

You don't want to punish the fast path by turning off ADMA, merely due 
to an issue relating to a non-fast-path command.

	Jeff




  reply	other threads:[~2007-04-13 16:46 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-10 23:23 [PATCH] libata: HPA support Alan Cox
2007-04-10 23:36 ` Jeff Garzik
2007-04-11  0:15   ` Alan Cox
2007-04-10 23:43 ` Kyle McMartin
2007-04-11 16:38 ` Kyle McMartin
2007-04-13 15:33 ` Kyle McMartin
2007-04-13 15:44   ` Kyle McMartin
2007-04-13 16:24     ` Jeff Garzik
2007-04-13 16:33       ` Kyle McMartin
2007-04-13 16:46         ` Jeff Garzik [this message]
2007-04-13 16:47         ` Kyle McMartin
2007-04-13 21:06           ` ROBERT HANCOCK
2007-04-17 16:10 ` Jeff Garzik
2007-04-17 18:41 ` Dave Jones
2007-04-17 19:15   ` Jeff Garzik
2007-04-17 19:30     ` Dave Jones
2007-04-17 19:34       ` Jesse Keating
2007-04-17 20:42         ` Jeff Garzik
2007-04-17 22:05           ` Kyle McMartin
2007-04-17 21:45   ` 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=461FB3ED.50708@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=kyle@canonical.com \
    --cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).