Hi Christoph, On 5/17/07, Christoph Hellwig <hch@xxxxxxxxxxxxx> wrote:
On Thu, May 17, 2007 at 11:11:10PM +0530, Satyam Sharma wrote: > Another command to /proc/scsi/scsi isn't a bad thought at all, considering Yes it is. /proc/scsi/scsi is a horrible interface and deprecated since the start of the 2.6 series.
What I have in mind is actually this: We implement commands to trigger the scsi_complete_async_scans() using *both* the (legacy, agreed) /proc/scsi/scsi interface _and_ using a sysfs attribute for this (either in /sys/module/scsi_mod/parameter/, using a module_param_call as Roland suggested, or, create a new /sys/module/scsi_mod/<whatever>/wait_..., whatever is appropriate). /proc/scsi/scsi is now deprecated _because_ the sysfs alternative became available, after all (we couldn't pull functionality / interfaces previously exposed to userspace from under them without giving equivalent alternatives anyway). However, Ben does have a point that we shouldn't force those using SCSI (and wishing to use the new async scanning feature) to depend on and use sysfs too, so those like him could use /proc/scsi/scsi. The idea is that with time sysfs gets its act together and thus becomes standard enough on all Linux boxen (much like /proc is today), and those like Ben could later switch to that. - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
