On Wed, Sep 10, 2008 at 09:29:18PM -0700, Nicholas A. Bellinger wrote: > On Wed, 2008-09-10 at 19:13 -0700, Joel Becker wrote: > > On Wed, Sep 10, 2008 at 06:42:46PM -0700, Nicholas A. Bellinger wrote: > > > So I am thinking about the following question: What would be the > > > preferred method for calling ct_group_ops->make_group() in order to > > > create the $CONFIGFS/target/$FABRIC struct config_item directly from > > > target_fabric_configfs_register() call? From there, the config group > > > hanging off $CONFIGFS/target/$FABRIC will be fabric dependent and > > > providing their own groups, items, depends, from the passed *fabric_cit. > > > How do I "simulate" a mkdir(2) configfs -> make_group() call coming from > > > the fabric module itself..? This would be assuming that both mkdir(2) > > > > That's precisely what you don't do with configfs. It's a > > defined "not to be done" thing. So there's no preferred way, there's no > > way at all. > > What you want do to is drive this from mkdir(). The > > make_group() will look up the sub-module it needs and return the > > appropriate item. > > > > Whew, good thing I asked about this case first.. :-) Can you give me a more complete description of what you're trying to do? that way I can maybe help with some suggestions. Joel -- "Win95 file and print sharing are for relatively friendly nets." - Paul Leach, Microsoft Joel Becker Principal Software Developer Oracle E-mail: joel.becker@xxxxxxxxxx Phone: (650) 506-8127 -- 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
