From: Jeff Garzik <jeff@garzik.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Mark Lord <liml@rtr.ca>,
linux-ide@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
gwendal@google.com
Subject: Re: [PROPOSED] ata: Report 16/32bit PIO as best we can
Date: Mon, 13 Apr 2009 12:32:57 -0400 [thread overview]
Message-ID: <49E36939.2050402@garzik.org> (raw)
In-Reply-To: <20090409140857.578a9146@lxorguk.ukuu.org.uk>
Alan Cox wrote:
>> But.. these do look rather suspiciously like sysfs attrs to me.
>
> I'd rather any future sysfs interface actually exposed something more
> meaningful. This is a legacy fixup 8)
>
>> We didn't have a sysfs in the IDE days (so Gadi added the klunky
>> procfs "settings" thing for there), but we do now.
>>
>> I'm happy to update hdparm to check sysfs if that's where this
>> ends up, or to do almost nothing for it if we stick with the ioctls.
>
> I'm not sure sysfs helps much anyway - you have to open the device file
> and keep it open while accessing the sysfs nodes anyway (something huge
> numbers of apps hopelessly fail to do so)
FWIW... here is the sysfs work I referred to (in a message sent several
days ago in this thread)...
http://lwn.net/Articles/294608/
Jeff
next prev parent reply other threads:[~2009-04-13 16:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-09 13:32 [PROPOSED] ata: Report 16/32bit PIO as best we can Alan Cox
2009-04-09 12:50 ` Jeff Garzik
2009-04-09 12:53 ` Alan Cox
2009-04-09 13:08 ` Jeff Garzik
2009-04-09 13:12 ` Alan Cox
2009-04-09 13:33 ` Jeff Garzik
2009-04-09 13:41 ` Alan Cox
2009-04-09 13:45 ` Jeff Garzik
2009-04-09 13:48 ` Tejun Heo
2009-04-09 13:49 ` Tejun Heo
2009-04-09 13:45 ` Tejun Heo
2009-04-09 13:58 ` Alan Cox
2009-04-09 14:02 ` Tejun Heo
2009-04-09 13:02 ` Mark Lord
2009-04-09 13:08 ` Alan Cox
2009-04-13 16:32 ` Jeff Garzik [this message]
2009-04-13 16:39 ` Alan Cox
2009-04-13 16:57 ` Jeff Garzik
2009-04-09 13:25 ` Jeff Garzik
2009-04-09 16:57 ` Mark Lord
2009-04-09 20:42 ` Jeff Garzik
2009-04-10 0:38 ` Douglas Gilbert
2009-04-10 0:47 ` 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=49E36939.2050402@garzik.org \
--to=jeff@garzik.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gwendal@google.com \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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.