RE: How to add/drop SCSI drives from within the driver?
From: Mukker, Atul
Date: Thu Dec 16 2004 - 09:42:24 EST
> On Wed, 2004-12-15 at 15:30 -0600, Matt Domsch wrote:
> > Do you plan to apply LSI's driver patch which adds the
> > ioctl to provide the mapping from logical drive address to
> HCTL value?
> > Both Dell and LSI have products which are lined up to use this new
> > ioctl because it's the most expedient thing to do,
> maintains internal
> > project schedules, etc, which delaying until this sysfs
> mechanism hits
> > will greatly impact those schedules. (I know, many folks on
> this list
> > don't care about business-side impacts of choices made on-list.)
> I'm strongly against adding this. The reason for that is that
> once an ioctl is added, it realistically will and can never go away.
This issue has gone from the utility of the ioctl in question (which has
been discussed in detail on the list) to now outright rejection of the
driver ioctls. If this is the idea, drivers would need to consciously move
the driver only ioctls to sysfs. Which may be good for simple ioctls like
these but might now be elegant for complex transfers. So, IMO, drivers need
both of the interfaces and should make a good judgment call on services
provided by each interface.
> that is no reason to foul up the kernel more.
The ioctl in question has been discussed in detail and was deemed
appropriate ioctl to provide important service to the management
applications for device hot plugging. Schedules are one side of the story,
but we must not overlook the importance of the reason to have this ioctl in
the first place. If there are other preferred ways to implement the similar
functionality, we would be more than happy to consider that.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/