From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Chuck Ebbert <cebbert@redhat.com>
Cc: Jeff Garzik <jeff@garzik.org>, Tejun Heo <htejun@gmail.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
akpm@osdl.org, linux-ide@vger.kernel.org
Subject: Re: [PATCH] libata: Add a drivers/ide style DMA disable
Date: Fri, 14 Sep 2007 21:54:10 +0200 [thread overview]
Message-ID: <200709142154.10607.bzolnier@gmail.com> (raw)
In-Reply-To: <46EAC225.70003@redhat.com>
On Friday 14 September 2007, Chuck Ebbert wrote:
> On 09/07/2007 06:47 PM, Jeff Garzik 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
2.6.24 will have "hdx=nodma"
> >>> libata.pata_dma=1 Disk DMA only
> >>> libata.pata_dma=2 ATAPI DMA only
> >>> libata.pata_dma=4 CF DMA only
> >>>
> >
> > FWIW -- as I noted to Alan personally at KS, I would rather drop the
> > "pata_" and have it apply to all, PATA or SATA.
> >
>
> Not sure that's a good idea for people who need to use it as a workaround.
> E.g. they might have DMA working on some SATA devices but not on PATA, and
> only want to disable the PATA DMA. Either adding a separate "sata_dma" or
> additional bitfields for SATA would be useful.
next prev parent reply other threads:[~2007-09-14 19:51 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 [this message]
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
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=200709142154.10607.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cebbert@redhat.com \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--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).