On Tue, 2005-01-25 at 19:10 +0100, Martin Peschke3 wrote: > Actually, you will find the adapter structure be an anchor for several > other objects, or lists of them respectively. We tried to organize > all the driver private data in a sane way. That means there is a tree > of objects representing the SAN topology, including target ports and > subordinate LUNs, many of which have an associated mid-layer structure. > I can't imagine that anybody would ever argue to collapse all that into > the adapter structure. So, why all the fuss about this particular object? > The generic services object has nothing to do with the adapter. It's about > fabric switch services, or certain well-known FC (target) ports, which can > be accessed in the fabric through an adapter. It's not local but remote, > like other targets, so to speak. We might also have chosen to call it > "fabric switch".
OK, take a look at this: http://marc.theaimsgroup.com/?l=linux-scsi&m=110546207223304 and tell me if it does everything you need. If it doesn't, you could try adding all the other bits to the fc transport class. James - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
