[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <47EBF7D0.6000901@zytor.com>
Date: Thu, 27 Mar 2008 12:38:56 -0700
From: "H. Peter Anvin" <hpa@...or.com>
To: Kay Sievers <kay.sievers@...y.org>
CC: 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@...l.org>,
Andrew Morton <akpm@...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 ?
Kay Sievers wrote:
>>
>> Probably something like /sys/class/block/MAJ:MIN
>
> "Devices directories" are not supposed to contain duplicate entries.
> It would slow-down, or may even break things.
>
>> or /sys/class/devnums/bMAJ:MIN?
>
> These are no devices belonging to the class "devnums", so it may
> confuse things which crawl these directories to get "all devices".
> Current coldplug-like setups will likely add duplicate devices with
> the wrong subsystem. There are also bus-devices with have a dev_t, and
> that will make them show up in /sys/class, which might confuse some
> tools too.
>
> I guess we will need to find some other solution as a /sys/class/ for
> that. And we must prefix the links with 'c' and 'b' because dev_t is
> not unique across char and block devices.
>
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.
-hpa
--
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