Re: Status of patch as168 (sysfs readonly max_sectors attribute)

[James Bottomley <James.Bottomley@steeleye.com>]

On Thu, 2004-01-15 at 14:30, Alan Stern wrote:
> If I understand this, you would like to see the low-level drivers manage
> these things for themselves by talking directly to the block layer,
> without having to go through the intermediate SCSI layers.  This would
> imply that any sysfs interface to max_sectors would then be the
> responsibility of the driver, since the block layer itself is much too
> generic to permit users to fiddle with the settings.
> 
> Correct?

Well, no, not exactly.  At issue are some of the SCSI template
parameters which are copied to the host structure and then simply passed
straight through to the block queue.

If you look in scsi_alloc_queue, it simply passes through these queue
parameters.  It's pretty pointless to have SCSI do anything about them
at all, so Jeff was saying we could just strip this out of the template
and the drivers and have them call the relevant blk_queue_ parameter
functions directly.

James


I personally think this would have to be done *before* any queue
activity, so probably in slave_alloc rather than slave_configure
(although there's no reason not to readjust in slave_configure).

James