> configfs or sysfs seem like a reasonably good fit. > configfs would seem the more natural fit since user mode creates the files and the directory hierarchy naturally fits the ring down of global -> HCA ->port specialization.
> Do you really need the configuration at the time of module load, or would it > work to tear down the device and reinitialize it if userspace decides to > update the configuration? In other words, at module load time, configure > yourself with default parameters, and then if userspace changes them, act > like a hot unplug followed by a hot plug, so you reinitialize your device from > scratch. > That is probably not possible. I'm guessing it is better to react to a "configfs" module parameter to wait on a completion and a "commit" configfs global attribute to release the driver to complete its initialization with a complete call once user mode has setup the attributes critical for initialization. Without setting configfs, qib would load as it currently does. It sure would be nice if there was a way to buffer keyed attribute information before a module is loaded and then provide an interface to read it when a module is initializing. Mike -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
