Neale Ferguson wrote: > Think of the IUCV driver like you would zfcp: You use the sysfs to set > up the connection parameters (for zfcp its WWPN/LUN for IUCV its > enduser/node/program) and then let the application use the simple > open/close/read/write/ioctl semantics. The reason why zfcp is like that is because it is a storage networking thing. It was written to fit into the storage model (scsi host adapter) but does'nt fit too well into the networking scheme. I agree that an IUCV device driver does not have any more obscurity then zfcp [in fact I consider your implementation less confusing], but since IUCV does'nt have to fit the storage model it can be cleaner than zfcp is from the networking perspective by using an address family.
Since our s390 code does already have an IUCV abstraction that your driver uses, there's nothing wrong with multiple soloutions here because they can interoperate cleanly. -- Carsten Otte IBM Linux technology center ARCH=s390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
