linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Lord <liml@rtr.ca>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: jeff@garzik.org, davej@redhat.com, linux-ide@vger.kernel.org
Subject: Re: [PATCH] libata: Add pata_dma option so users can disable pata_dma as they can with old-ide
Date: Fri, 22 Jun 2007 12:53:03 -0400	[thread overview]
Message-ID: <467BFE6F.7050300@rtr.ca> (raw)
In-Reply-To: <20070622165221.2ce648f6@the-village.bc.nu>

Alan Cox wrote:
> On Fri, 22 Jun 2007 11:01:09 -0400
> Mark Lord <liml@rtr.ca> wrote:
> 
>> Alan Cox wrote:
>>> Allow
>>>
>>> 	libata.pata_dma=0
>>>
>>> to disable DMA (default is 1)
>>>
>>> SATA is unaffected as disabling DMA for SATA makes no sense at all.
>>>
>>> Signed-off-by: Alan Cox <alan@redhat.com>
>> Alan,
>>
>> Should we really be piling up like this on global boot/module options
>> rather than run-time flags on individual channels/devices ?
>>
>> I can imagine systems with internal notebook drives that want dma=1,
>> plus Cardbus CF devices that require dma=0.
>>
>> With a single global flag, how does one do that?
> 
> We need proper tuning as well but there is huge value (with distro hat
> on especially) in a single "try this to get it installed and then we can
> debug it" button. Same with the old IDE. Trying to guide users through
> selecting specific channels/devices is going to be painful. I want
> something that I can tell people to get them 'off the ground' and work
> with them to sort the rest.

Oh for sure.  I'm just thinking that some form of on-the-fly tunable
would be of even greater value here, in addition to the boot/load default flag.

I think a /sys/ "dma" attribute (pick a name) might be most appropriate,
or we just just implement HDIO_[GS]ET_DMA as a simpler/lazier mechanism.

Cheers


  reply	other threads:[~2007-06-22 16:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-22 13:49 [PATCH] libata: Add pata_dma option so users can disable pata_dma as they can with old-ide Alan Cox
2007-06-22 15:01 ` Mark Lord
2007-06-22 15:52   ` Alan Cox
2007-06-22 16:53     ` Mark Lord [this message]
2007-06-22 19:04       ` Bartlomiej Zolnierkiewicz
2007-06-22 19:26         ` Alan Cox
2007-06-23 17:41           ` Bartlomiej Zolnierkiewicz

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=467BFE6F.7050300@rtr.ca \
    --to=liml@rtr.ca \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davej@redhat.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).