Changes between Version 5 and Version 6 of Internal/NewNodeAgent

Timestamp:

Sep 24, 2014, 12:45:34 AM (10 years ago)

Author:

ssugrim

Comment:

—

Internal/NewNodeAgent

@@ -58 +58 @@
  * All devices will not know their device name during creation (default is nil). All dev_driver classes will be instantiated at startup, however none of them will be activated (with the exception of eth1). When a device need to be used. It will have to be activated. Once activated (that is once the module is loaded) the agent will give names to the respective objects now that they have been created. This is essentially how the logical names are bound to the dev names (a logic managed by the agent, not the dev).
 ----
-''' 9/1/2014 '''
+''' 9/22/2014 '''
  * It may be necissary to have multiple driver modules for a single device. The recurrent case is the iwldvm module. It gets loaded if we load iwlwifi but it depends on iwlwifi. Thus when you load iwlwifi, you can not unload it with out first unloading iwldvm. Because iwlwifi and athXk both depend on cfg802, when the iwldvm module is unloaded with ''modprobe -r iwldvm'', iwlwifi is not unloaded. 
+
+----
+''' 9/23/2014 '''
+ * Node agent it self should check what modules are already loaded and create instances of the module classes for modules that are already loaded. It will push in a refrence to it self, so that the refrence buffer can never go empty. 
+ * There will need to be a structure that maps pci-id <-> modulename <-> deviceClass. This structure will need to be known to node agent.