Documentation: devlink: extend reload-reinit description
Be more explicit about devlink entities that may stay and that have to be removed during reload reinit action. Signed-off-by: Jiri Pirko <jiri@nvidia.com> Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@intel.com> Signed-off-by: Paolo Abeni <pabeni@redhat.com>
This commit is contained in:
parent
e35174263f
commit
15d74e6588
@ -22,8 +22,17 @@ By default ``driver_reinit`` action is selected.
|
||||
* - ``driver-reinit``
|
||||
- Devlink driver entities re-initialization, including applying
|
||||
new values to devlink entities which are used during driver
|
||||
load such as ``devlink-params`` in configuration mode
|
||||
``driverinit`` or ``devlink-resources``
|
||||
load which are:
|
||||
|
||||
* ``devlink-params`` in configuration mode ``driverinit``
|
||||
* ``devlink-resources``
|
||||
|
||||
Other devlink entities may stay over the re-initialization:
|
||||
|
||||
* ``devlink-health-reporter``
|
||||
* ``devlink-region``
|
||||
|
||||
The rest of the devlink entities have to be removed and readded.
|
||||
* - ``fw_activate``
|
||||
- Firmware activate. Activates new firmware if such image is stored and
|
||||
pending activation. If no limitation specified this action may involve
|
||||
|
Loading…
Reference in New Issue
Block a user