devlink-dev - Man Page

DEV - specifies the devlink device to show. If this argument is omitted all devices are listed.

Format is: BUS_NAME/BUS_ADDRESS

mode { legacy | switchdev }

Set eswitch mode

legacy - Legacy SRIOV

switchdev - SRIOV switchdev offloads

inline-mode { none | link | network | transport }

Some HWs need the VF driver to put part of the packet headers on the TX descriptor so the e-switch can do proper matching and steering.

none - None

link - L2 mode

network - L3 mode

transport - L4 mode

encap-mode { none | basic }

Set eswitch encapsulation support

none - Disable encapsulation support

basic - Enable encapsulation support

name PARAMETER

Specify parameter name to set.

value VALUE

New value to set.

cmode { runtime | driverinit | permanent }

Configuration mode in which the new value is set.

runtime - Set new value while driver is running. This configuration mode doesn't require any reset to apply the new value.

driverinit - Set new value which will be applied during driver initialization. This configuration mode requires restart driver by devlink reload command to apply the new value.

permanent - New value is written to device's non-volatile memory. This configuration mode requires hard reset to apply the new value.

name PARAMETER Specify parameter name to show. If this argument is omitted all parameters supported by devlink devices are listed.

DEV - Specifies the devlink device to reload.

netns { PID | NAME | ID } - Specifies the network namespace to reload into, either by pid, name or id.

action { driver_reinit | fw_activate } - Specifies the reload action required. If this argument is omitted driver_reinit action will be used. Note that even though user asks for a specific action, the driver implementation might require to perform another action alongside with it. For example, some driver do not support driver reinitialization being performed without fw activation. Therefore, the devlink reload command returns the list of actions which were actrually performed.

driver_reinit - Driver entities re-initialization, applying devlink-param and devlink-resource values.

fw_activate - Activates new firmware if such image is stored and pending activation. If no limitation specified this action may involve firmware reset. If no new image pending this action will reload current firmware image.

limit no_reset - Specifies limitation on reload action. If this argument is omitted limit is unspecified and the reload action is not limited. In such case driver implementation may include reset or downtime as needed to perform the actions.

no_reset - No reset allowed, no down time allowed, no link flap and no configuration is lost.

Display device information provided by the driver. This command can be used to query versions of the hardware components or device components which can't be updated ( fixed ) as well as device firmware which can be updated. For firmware components running displays the versions of firmware currently loaded into the device, while stored reports the versions in device's flash. Running and stored versions may differ after flash has been updated, but before reboot.

DEV - specifies the devlink device to show. If this argument is omitted all devices are listed.

DEV - specifies the devlink device to write to.

file PATH - Path to the file which will be written into device's flash. The path needs to be relative to one of the directories searched by the kernel firmware loader, such as /lib/firmware.

component NAME - If device stores multiple firmware images in non-volatile memory, this parameter may be used to indicate which firmware image should be written. The value of NAME should match the component names from devlink dev info and may be driver-dependent.

DEV - specifies the devlink device. If this argument is omitted all selftests for devlink devices are listed.

DEV - specifies the devlink device to execute selftests.

id ID... - The value of ID(s) should match the selftests shown in devlink dev selftests show to execute selftests on the devlink device. If this argument is omitted all selftests supported by devlink devices are executed.