[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <47E9853C.1030506@zytor.com>
Date: Tue, 25 Mar 2008 16:05:32 -0700
From: "H. Peter Anvin" <hpa@...or.com>
To: Greg KH <gregkh@...e.de>
CC: Randy Dunlap <randy.dunlap@...cle.com>, Mark Lord <lkml@....ca>,
Jens Axboe <axboe@...nel.dk>, Jeff Garzik <jgarzik@...ox.com>,
Tejun Heo <htejun@...il.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 ?
> How does this have anything to do with boot times? Do you really have a
> foolish shell script that iteratorates over every single disk in the
> sysfs tree for every disk? What does it do that for?
Any time you want to get the sysfs information for a filesystem which is
already mounted, that's what you're forced to do.
> I thought we were talking about 2TB disks here, with a proposed new
> ioctl, not foolishness of boot scripts...
I pointed out that having a way to map device numbers to sysfs
directories would have the same effect, *and* would be usable for other
purposes. I'd rather see that than a new ioctl, and another, and another...
ioctl()s are also nasty since they're generally root-only (or rather,
device-owner only). Since the information is already in sysfs, there is
no benefit to this hiding. Otherwise one could consider a ioctl() "give
me the sysfs name of this device."
-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