[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4804B1E0.10200@rtr.ca>
Date: Tue, 15 Apr 2008 09:47:12 -0400
From: Mark Lord <liml@....ca>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Dan Williams <dan.j.williams@...el.com>,
"H. Peter Anvin" <hpa@...or.com>,
Kay Sievers <kay.sievers@...y.org>,
Tejun Heo <htejun@...il.com>, Mark Lord <lkml@....ca>,
Greg KH <gregkh@...e.de>, Jens Axboe <axboe@...nel.dk>,
Jeff Garzik <jgarzik@...ox.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Linux Kernel <linux-kernel@...r.kernel.org>,
IDE/ATA development list <linux-ide@...r.kernel.org>,
linux-scsi <linux-scsi@...r.kernel.org>
Subject: Re: What to do about the 2TB limit on HDIO_GETGEO ?
Andrew Morton wrote:
> On Fri, 11 Apr 2008 16:25:32 -0700 "Dan Williams" <dan.j.williams@...el.com> wrote:
>
>>> It doesn't really seem to be to belong under class at all. I would suggest
>>> /sys/dev/char/ and /sys/dev/block/, for char and block respectively.
>>>
>> This thread fizzled out without a patch... here goes:
>>
>> ...
>>
>> sysfs: add /sys/dev/{char,block} to lookup sysfs path by major:minor
>
> Crickets are chirping and I can't remember what the conclusion to all this
> was. In fact the thread was more than ten-deep so I probably fell asleep.
..
Last I recall, Greg was vehemently opposed to having direct path access
by device number in sysfs, but many other people saw benefit.
Myself (the originator), I simply decided that my sysfs access code has
to work with older kernels too, so for now I'm just doing a brute force
tree search to find things in sysfs. I did get the code size down smaller
for it, but it's still a pain.
When the direct access feature goes in, I'll just change my code to try it first,
and then still fall back to the tree search method on failure.
> I queued it up so that others cannot do the same ;)
..
Good!
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists