Nicholas A. Bellinger, on 11/15/2010 11:19 PM wrote: >> I think that Vlad has already explained several times why ConfigFS is >> not suited for the needs of a storage target: a storage target must >> not only be able to accept configuration information from userspace >> but must also be able to create new directories and file nodes itself. >> See e.g. this message from October 6: >> http://kerneltrap.org/mailarchive/linux-kernel/2010/10/6/4628664. > > Sorry, but this post explains nothing but a single misguided and > uninformed opinion, with no hard facts on the actual usage of a native > configfs control plane within target mode infrastructure. What is "misguided and uninformed opinion"? That you can't with ConfigFS serve real life needs for target driver developers and can't create targets for hardware target ports from withing the kernel and instead enforce users to clumsy workarounds to somehow magically know their names to manually perform "mkdir target_name"? The same problem exists for all other objects where you need to create ConfigFS entries (directories), like for per-session/per-initiator statistics or default ACLs. ConfigFS is just too simple to serve real life needs of a SCSI target subsystem. Vlad -- 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
