Hi Nicholas, Thank you for your reply. On Fri, 18 Oct 2013 12:25:54 -0700, Nicholas A. Bellinger wrote : > > Also, since the iSCSI target is implemented in the > > Linux kernel, would that make sense to implement an iSNS client in > > the kernel too? Are there plans for that or do you think it's > > better to implement this feature in user space? > > > > There is no requirement for the iSNS client to reside kernel-space, > and it makes the most sense for it to be a user-space process. > > Really, all a simple iSNS client needs to do is walk the configfs / > rtslib hierarchy, and report the current iscsi-target configuration > (eg: TargetName+TargetPortalGroupTag + Network Portals) to the iSNS > server. > > It should also be smart enough to query and unregister entities that > no longer exist in the local configuration. OK. Maybe it should also run as a service in order to be able to reply to Entity Status Inquiry (ESI) messages. http://tools.ietf.org/html/rfc4171#section-5.6.5.13 I may consider writing such an iSNS client. If so, I will not start from scratch but will probably re-use some code from IET. Best regards, -- Christophe Vu-Brugier -- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
