Re: [RFC] scsi host sysfs support again [0/4]

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

On Mon, 2003-05-05 at 03:33, Mike Anderson wrote:
> Example tree:
> 
> # tree /sys/class/scsi_host
> /sys/class/scsi_host
> |-- host0
> |   |-- cmd_per_lun
> |   |-- device -> ../../../devices/pci0/00:09.0/host0
> |   |-- host_busy
> |   |-- sg_tablesize
> |   |-- unchecked_isa_dma
> |   `-- unique_id

Could you elaborate a bit more on why the host properties are under the
class tree, but the scsi_device properties are under the device tree.

I think this could be my misunderstanding of the class concept:  I
thought it was going to be a unifying abstraction, e.g. a class for all
tape devices (be they SCSI, ide or the oddball qic ones) that would
export a unifying interface that all tapes could use.  Therefore, you
have a device with a set of intrinsic properties exposed in the device
tree plus a set of classes whose interfaces it chooses to export.

I could see us adding a scsi_device class and moving all the device
properties under there too, I suppose.

What I think I'm looking for is clarification of what is a "class
property" vs what is a "device property"

James