diff options
author | Maor Gottlieb <maorg@mellanox.com> | 2019-08-28 15:10:54 +0300 |
---|---|---|
committer | Saeed Mahameed <saeedm@mellanox.com> | 2019-09-03 12:54:24 -0700 |
commit | e890acd5ff18a0144967d0289869fe5f0415d399 (patch) | |
tree | a50147dc54aaa6a520223745a83b76f8795d78bf /net/can/af_can.c | |
parent | 8463daf17e800c11d0f837aed2e2813391593916 (diff) | |
download | linux-stable-e890acd5ff18a0144967d0289869fe5f0415d399.tar.gz linux-stable-e890acd5ff18a0144967d0289869fe5f0415d399.tar.bz2 linux-stable-e890acd5ff18a0144967d0289869fe5f0415d399.zip |
net/mlx5: Add devlink flow_steering_mode parameter
Add new parameter (flow_steering_mode) to control the flow steering
mode of the driver.
Two modes are supported:
1. DMFS - Device managed flow steering
2. SMFS - Software/Driver managed flow steering.
In the DMFS mode, the HW steering entities are created through the
FW. In the SMFS mode this entities are created though the driver
directly.
The driver will use the devlink steering mode only if the steering
domain supports it, for now SMFS will manages only the switchdev eswitch
steering domain.
User command examples:
- Set SMFS flow steering mode::
$ devlink dev param set pci/0000:06:00.0 name flow_steering_mode value "smfs" cmode runtime
- Read device flow steering mode::
$ devlink dev param show pci/0000:06:00.0 name flow_steering_mode
pci/0000:06:00.0:
name flow_steering_mode type driver-specific
values:
cmode runtime value smfs
Signed-off-by: Maor Gottlieb <maorg@mellanox.com>
Signed-off-by: Saeed Mahameed <saeedm@mellanox.com>
Diffstat (limited to 'net/can/af_can.c')
0 files changed, 0 insertions, 0 deletions