All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: akpm@osdl.org, linux-ide@vger.kernel.org
Subject: Re: [PATCH] libata: Add a drivers/ide style  DMA disable
Date: Tue, 02 Oct 2007 12:38:48 -0400	[thread overview]
Message-ID: <47027418.1080008@garzik.org> (raw)
In-Reply-To: <20070822233710.415faaf0@the-village.bc.nu>

Alan Cox wrote:
> This is useful when debugging, handling problem systems, or for
> distributions just to get the system installed so it can be sorted
> out later.
> 
> This is a bit smarter than the old IDE one and lets you do
> 
> libata.pata_dma=0		Disable all PATA DMA like old IDE
> libata.pata_dma=1		Disk DMA only
> libata.pata_dma=2		ATAPI DMA only
> libata.pata_dma=4		CF DMA only
> 
> (or combinations thereof - 0,1,3 being the useful ones I suspect)
> 
> (I've split CF as it seems to be a seperate case of pain and suffering
> different to the others and caused by assorted PIO wired adapters etc)
> 
> SATA is not affected - for one its not clear it makes sense to disable
> DMA for SATA if even always possible, for two we've seen no failure 
> evidence to justify needing to support this kind of hammer on SATA.
> 
> Signed-off-by: Alan Cox <alan@redhat.com>

applied, after making it work on SATA too



      parent reply	other threads:[~2007-10-02 16:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-22 22:37 [PATCH] libata: Add a drivers/ide style DMA disable Alan Cox
2007-09-07  3:58 ` Tejun Heo
2007-09-07 22:47   ` Jeff Garzik
2007-09-08  6:01     ` Tejun Heo
2007-09-08 18:42     ` Alan Cox
2007-09-14 17:17     ` Chuck Ebbert
2007-09-14 19:54       ` Bartlomiej Zolnierkiewicz
2007-09-19 15:53 ` Chuck Ebbert
2007-09-19 16:40   ` Alan Cox
2007-09-20  1:18   ` Tejun Heo
2007-10-02 16:38 ` 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=47027418.1080008@garzik.org \
    --to=jeff@garzik.org \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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 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.