From: Greg KH <gregkh@suse.de>
To: Mark Lord <lkml@rtr.ca>
Cc: "H. Peter Anvin" <hpa@zytor.com>, Jens Axboe <axboe@kernel.dk>,
Jeff Garzik <jgarzik@pobox.com>, Tejun Heo <htejun@gmail.com>,
Linus Torvalds <torvalds@osdl.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
IDE/ATA development list <linux-ide@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: What to do about the 2TB limit on HDIO_GETGEO ?
Date: Tue, 25 Mar 2008 12:25:15 -0700 [thread overview]
Message-ID: <20080325192515.GA24234@suse.de> (raw)
In-Reply-To: <47E9383F.3050908@rtr.ca>
On Tue, Mar 25, 2008 at 01:37:03PM -0400, Mark Lord wrote:
> H. Peter Anvin wrote:
>> Mark Lord wrote:
>>>
>>> Yeah, that would be just as good, really. Maybe even better.
>>>
>>> Mark Lord wrote (later on):
>>>> Instead, software has to search everything inside /sys/block/
>>>> looking for a "dev" file whose contents match,
>>>> rather than just trying to access something like this:
>>>>
>>>> /sys/block/8:1/start
>>>> or
>>>> /sys/block/majors/8/minors/1/start
>>>>
>>>> Or any one of a number of similar ways to arrange it.
>>> ..
>> It shouldn't be under /sys/block... there are enough many things that scan
>> /sys/block and assume any directory underneath it has the current format.
> ..
>
> So long as we only add things, and not remove them, then any software
> that scans /sys/block/ shouldn't care, really.
>
> But yes, it could go elsewhere, too.
> Perhaps a /sys/dev/ directory, populated with symbolic links
> (or hard links?) back to the /sys/block/ entries, something like this:
>
> /sys/dev/block/8:0 -> ../../../block/sda
> /sys/dev/block/8:1 -> ../../../block/sda/sda1
> /sys/dev/block/8:2 -> ../../../block/sda/sda2
> ...
>
> That's just a suggestion, really.
> And what about character devices?
>
> Perhaps Greg will chime in.
I've been waiting to see if sanity will take hold of anyone here.
Come on people, adding symlinks for device major:minor numbers in sysfs
to save a few 10s of lines of userspace code? Can things get sillier?
You can add a single udev rule to probably build these in a tree in /dev
if you really need such a thing...
And what's wrong with your new ioctl recomendation?
greg k-h
next prev parent reply other threads:[~2008-03-25 19:25 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <47E875AD.1000901@rtr.ca>
2008-03-25 4:02 ` What to do about the 2TB limit on HDIO_GETGEO ? Mark Lord
2008-03-25 4:19 ` Andrew Morton
2008-03-25 5:13 ` H. Peter Anvin
2008-03-25 13:37 ` Mark Lord
2008-03-25 13:55 ` H. Peter Anvin
2008-03-25 17:37 ` Mark Lord
2008-03-25 19:25 ` Greg KH [this message]
2008-03-25 19:34 ` Randy Dunlap
2008-03-25 20:36 ` H. Peter Anvin
2008-03-25 21:20 ` Greg KH
2008-03-25 21:26 ` H. Peter Anvin
2008-03-25 23:00 ` Greg KH
2008-03-25 23:05 ` H. Peter Anvin
2008-03-25 23:22 ` Greg KH
2008-03-27 19:05 ` Matthew Wilcox
2008-03-26 0:34 ` Mark Lord
2008-03-26 0:54 ` Tejun Heo
2008-03-26 3:38 ` Greg KH
2008-03-26 4:24 ` Tejun Heo
2008-03-26 6:04 ` H. Peter Anvin
2008-03-27 19:29 ` Kay Sievers
2008-03-27 19:38 ` H. Peter Anvin
2008-04-11 23:25 ` Dan Williams
2008-04-15 7:18 ` Andrew Morton
2008-04-15 13:47 ` Mark Lord
2008-04-15 14:20 ` James Bottomley
2008-04-15 18:16 ` H. Peter Anvin
2008-04-15 23:43 ` Dan Williams
2008-04-16 20:55 ` patch sysfs-add-sys-dev-char-block-to-lookup-sysfs-path-by-major-minor.patch added to gregkh-2.6 tree gregkh
2008-04-16 20:55 ` gregkh
2008-04-16 20:55 ` gregkh
2008-03-27 18:51 ` What to do about the 2TB limit on HDIO_GETGEO ? Kay Sievers
2008-03-27 18:55 ` H. Peter Anvin
2008-03-27 19:03 ` Kay Sievers
2008-03-25 15:17 ` James Bottomley
2008-03-25 17:31 ` Mark Lord
2008-03-25 19:32 ` James Bottomley
2008-03-25 17:45 ` Greg Freemyer
2008-03-25 17:52 ` Randy Dunlap
2008-03-25 18:09 ` Matthew Wilcox
2008-03-26 9:58 ` Boaz Harrosh
2008-03-30 4:28 ` Matt Domsch
[not found] ` <alpine.LFD.1.00.0803242254020.2775@woody.linux-foundation.org>
2008-03-25 13:34 ` Mark Lord
2008-03-25 13:51 ` Greg Freemyer
2008-03-25 14:31 ` Ric Wheeler
2008-03-25 15:25 ` Andrew Paprocki
2008-03-25 15:34 ` Matthew Wilcox
2008-03-25 15:48 ` Ric Wheeler
2008-03-25 16:47 ` Theodore Tso
2008-03-25 20:51 ` Theodore Tso
2008-03-25 20:51 ` Theodore Tso
2008-03-25 20:51 ` Theodore Tso
[not found] <abhxL-xC-7@gated-at.bofh.it>
[not found] ` <abhRd-1bf-15@gated-at.bofh.it>
[not found] ` <ablib-2zv-65@gated-at.bofh.it>
[not found] ` <abn0B-735-35@gated-at.bofh.it>
[not found] ` <abna7-7jK-3@gated-at.bofh.it>
[not found] ` <abo6b-11J-9@gated-at.bofh.it>
[not found] ` <aboSP-2Wf-29@gated-at.bofh.it>
[not found] ` <aboSP-2Wf-27@gated-at.bofh.it>
[not found] ` <abqrq-6eX-29@gated-at.bofh.it>
[not found] ` <abqrq-6eX-27@gated-at.bofh.it>
[not found] ` <abqKM-6Ka-13@gated-at.bofh.it>
2008-03-26 11:30 ` Bodo Eggert
2008-03-26 11:30 ` Bodo Eggert
2008-03-27 3:52 ` Greg KH
2008-03-27 4:57 ` H. Peter Anvin
2008-03-27 14:45 ` Mark Lord
2008-03-27 15:15 ` Greg KH
2008-03-26 11:30 ` Bodo Eggert
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=20080325192515.GA24234@suse.de \
--to=gregkh@suse.de \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=hpa@zytor.com \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lkml@rtr.ca \
--cc=torvalds@osdl.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.