On Wed, 23 Mar 2011 23:59:40 -0700 "Nicholas A. Bellinger" <nab@xxxxxxxxxxxxxxx> wrote: > > > But reading the of the configfs layout is not the problem, yes..? > > > > I don't think so. The user space doesn't cache the configfs info. So > > the rule is pretty simple. > > It's more complicated than that. We have to then start referencing > things like struct se_node_acl usage to userspace when locating an > explict NodeACL during login. What happens if the explict NodeACL is > removed from configfs context while userspace code is running..? What > happens if the entire TPG is removed during an active userspace login..? > It all has to be sychronized with a userspace daemon through a single > thread that needs to know about the network portals, TPG layout and > explict NodeACls in order to complete a iSCSI login. Such can happen even if you do in kernel. During the login process, the configuration may change. You can't lock the configuration during the login process even if you do all in kernel. We need no synchronization at all with the user space approach. -- To unsubscribe from this list: 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
