You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently KMM supports 2 mode for deploying kernel module/s via single KMM Module
deploying one kernel module via a single Module (module name is specified in the spec)
deploying multiple kernel modules, in case there is a symbols dependency between modules (as defined by module.dep). In this case the main module is specified in the Module, and running modprobe command on with that specific module will load all other modules that defines dependency for the main module
In case customer want to deploy multiple, independent kernel modules via single Module, the following sequence needs to be defined:
define dependency between kernel modules in the /etc/modprobe.d/softdep.conf file.
Example: if customer has 3 modules in the image (simple-a, simple-b, simple-c) then the following definitions in the softdep.conf file will set the order of loading:
i don't see bug difference between creating ConfigMap with a specific format, and asking user to add the file with that specific format to DriverContainer image. But maybe we can add a field to the ModuleLoaderContainerSpec where user will define the order in simple terms, and then we will translate it into softdep.conf format, and use your idea with ConfigMap to insert it into ModuleLoader image. That way we hide implementation, and can change it if needed.
And it will also help in case we need to use in-cluster build
Currently KMM supports 2 mode for deploying kernel module/s via single KMM
Module
Module
(module name is specified in the spec)module.dep
). In this case the main module is specified in theModule
, and runningmodprobe
command on with that specific module will load all other modules that defines dependency for the main moduleIn case customer want to deploy multiple, independent kernel modules via single
Module
, the following sequence needs to be defined:create
/etc/modprobe.d/softdep.conf
file inside ModuleLoader imagedefine dependency between kernel modules in the
/etc/modprobe.d/softdep.conf
file.Example: if customer has 3 modules in the image (
simple-a
,simple-b
,simple-c
) then the following definitions in thesoftdep.conf
file will set the order of loading:The order of loading will be:
simple-c
, thensimple-b
, thensimple-a
The order of unloading will be reversed:
simple-a
, thensimple-b
, thensimple-c
The text was updated successfully, but these errors were encountered: