Changes between Version 3 and Version 4 of Internal/NewNodeAgent

Timestamp:

Sep 23, 2014, 6:11:13 PM (10 years ago)

Author:

ssugrim

Comment:

—

Internal/NewNodeAgent

@@ -11 +11 @@
 ----
 ''' Design Notes: '''
+
+'''kmodule.rb'''
+Moving all the functionality of module handling into a separate class. There may be a need to have drivers load multiple modules. Additionally the module class needs to keep track of how many devices are using one module (as there may be many to one). The unload method should only unload if the last reference asks it to (all other references have de-registered). 
 
 ''' nodeagent.rb: '''
@@ -42 +45 @@
 ----
 Observations: 
+----
+''' 9/1/2014 '''
  * active? is defined at "Ready to be configured". If a device is set to active, it is read to accept config commands.
  * Activation should check if the module is loaded before loading it. 
- * 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). 
+ * 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 '''
+ * 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.