diff options
| author |   Michal Jaron <michalx.jaron@intel.com> | 2022-10-24 10:19:42 +0200 |
|---|---|---|
| committer |   Tony Nguyen <anthony.l.nguyen@intel.com> | 2022-12-05 08:30:51 -0800 |
| commit | 82e0572b23029b380464fa9fdc125db9c1506d0a (patch) | |
| tree | c1ef94fbb0207017007ff96b586d97f3b26d937f /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | net: mvneta: Prevent out of bounds read in mvneta_config_rss() (diff) | |
| download | wireguard-linux-82e0572b23029b380464fa9fdc125db9c1506d0a.tar.xz wireguard-linux-82e0572b23029b380464fa9fdc125db9c1506d0a.zip | |
i40e: Fix not setting default xps_cpus after reset
During tx rings configuration default XPS queue config is set and
__I40E_TX_XPS_INIT_DONE is locked. __I40E_TX_XPS_INIT_DONE state is
cleared and set again with default mapping only during queues build,
it means after first setup or reset with queues rebuild. (i.e.
ethtool -L <interface> combined <number>) After other resets (i.e.
ethtool -t <interface>) XPS_INIT_DONE is not cleared and those default
maps cannot be set again. It results in cleared xps_cpus mapping
until queues are not rebuild or mapping is not set by user.
Add clearing __I40E_TX_XPS_INIT_DONE state during reset to let
the driver set xps_cpus to defaults again after it was cleared.
Fixes: 6f853d4f8e93 ("i40e: allow XPS with QoS enabled")
Signed-off-by: Michal Jaron <michalx.jaron@intel.com>
Signed-off-by: Kamil Maziarz <kamil.maziarz@intel.com>
Tested-by: Gurucharan <gurucharanx.g@intel.com> (A Contingent worker at Intel)
Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions