From: Jeff Garzik <jeff@garzik.org>
To: Alan <alan@lxorguk.ukuu.org.uk>
Cc: Mark Lord <lkml@rtr.ca>, Patrick Ale <patrick.ale@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: hdparm for lib_pata
Date: Mon, 05 Feb 2007 16:19:28 -0500 [thread overview]
Message-ID: <45C79F60.50305@garzik.org> (raw)
In-Reply-To: <20070205190947.680f2237@localhost.localdomain>
Alan wrote:
>> Userspace PIO mode changes are NOT a good idea,
>
> I would disagree there, but they are not high priority. We do need to
> allow set_features/xfer but we need to snoop it and mode set properly
> around it. There are cases you want to control this, more so admittedly
> for DMA speeds.
*Bingo*
That's the entire reason why libata does not support hdparm changing
modes, etc.: there is a lot involved in allowing random SET FEATURES -
XFER MODE commands from userspace. In some cases you have to stop all
traffic on ports B,C,D,... in order to change the speed on port A.
Jeff
next prev parent reply other threads:[~2007-02-05 21:19 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-03 8:41 hdparm for lib_pata Patrick Ale
2007-02-03 8:55 ` Patrick Ale
2007-02-03 12:07 ` Rene Rebe
2007-02-05 18:13 ` Mark Lord
2007-02-05 19:09 ` Alan
2007-02-05 21:19 ` Jeff Garzik [this message]
2007-02-05 19:21 ` Patrick Ale
[not found] <fa.L/RjDlo6Njb5Jt7/9ENZuiASoV0@ifi.uio.no>
2007-02-03 19:14 ` Robert Hancock
2007-02-03 23:15 ` Stephen Clark
2007-02-03 23:28 ` Robert Hancock
2007-02-06 17:44 ` Bill Davidsen
2007-02-06 18:45 ` Mark Lord
2007-02-06 21:05 ` Jeff Garzik
2007-02-06 23:45 ` Robert Hancock
2007-02-03 23:44 ` Patrick Ale
2007-02-04 0:11 ` Stephen Clark
2007-02-04 0:18 ` Patrick Ale
2007-02-05 11:00 ` Patrick Ale
2007-02-05 14:23 ` Robert Hancock
2007-02-05 16:21 ` Patrick Ale
2007-02-05 18:15 ` Mark Lord
2007-02-06 17:49 ` Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2007-02-07 10:55 Adam J. Richter
2007-02-07 11:47 ` Patrick Ale
2007-02-08 2:16 Adam J. Richter
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=45C79F60.50305@garzik.org \
--to=jeff@garzik.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
--cc=patrick.ale@gmail.com \
/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