On Mon, Sep 12, 2005 at 07:00:54PM +1000, Douglas Gilbert wrote: > > +This is a link to the tree(1) program, very useful in > > +viewing the SAS domain: > > +ftp://mama.indstate.edu/linux/tree/ > > +I expect user space applications to actually create a > > +graphical interface of this. > > + > > +That is, the sysfs domain tree doesn't show or keep state if > > +you e.g., change the meaning of the READY LED MEANING > > +setting, but it does show you the current connection status > > +of the domain device. > > So in that case, user applications should ignore READY > LED MEANING in sysfs and ask the device directly. > For example: > sdparm --get RLM --transport sas /dev/sda > > > +Keeping internal device state changes is responsibility of > > +upper layers (Command set drivers) and user space. > > ... and what about multiple initiators sitting on different > machines? Should they be responsible for: > 1) finding out about one another > 2) and keeping the sysfs tree in the other machine > in sync when one changes READY LED MEANING > (or anything else)? > > Putting distributed state information in sysfs and then > passing off the responsibility for maintaining its state > (because it is a difficult problem) brings into question > the wisdom of the strategy. If you looks at what the other transport classes do is that they put information at discovery time into sysfs, but try to refresh it on every access. IMHO that makes a lot of sense, and should be done that way in the final SAS transport class. - : 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
