Hi, I have been working on implementing autologin support for objectlayout driver in pNFS client. This feature would allow pNFS object clients to receive an URI (e.g. iscsi://<IP>:<PORT>) of a target OSD via GETDEVICEINFO rpc from the server. Object layout driver would then pass this information to an user space daemon which would perform the login task depending on the protocol involved (e.g. Iscsi login using iscsiadm). For userspace daemon, we have 2 implementation choices. 1. Add new daemon (say, osdlogind) to nfs-utils which would process the upcalls from object layout driver via rpc_pipefs (very similar to the way blkmapd works) 2. Modify blkmapd in nfs-utils package to be able to process upcalls from the object layout driver and add new functionality to process these messages. I think, (1) above is the simplest and cleanest way to go about implementing this. (2) adds an indirect dependency between block layout driver and object layout driver if they were to share the same rpc pipe to communicate with user space. Currently I have a simple implementation of 'osdlogind' coded up which borrows its design heavily from 'blkmapd' code. Please let me know what would be the preferred way to go about this. Thanks in advance for your inputs. Sachin Bhamare Panasas Inc. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
