[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CYYPR11MB8429C68B610E3FBD13E333BBBD052@CYYPR11MB8429.namprd11.prod.outlook.com>
Date: Thu, 11 Apr 2024 12:14:22 +0000
From: "Pucha, HimasekharX Reddy" <himasekharx.reddy.pucha@...el.com>
To: "Polchlopek, Mateusz" <mateusz.polchlopek@...el.com>,
"intel-wired-lan@...ts.osuosl.org" <intel-wired-lan@...ts.osuosl.org>
CC: "andrew@...n.ch" <andrew@...n.ch>, "jiri@...nulli.us" <jiri@...nulli.us>,
"Wilczynski, Michal" <michal.wilczynski@...el.com>, "Polchlopek, Mateusz"
<mateusz.polchlopek@...el.com>, "netdev@...r.kernel.org"
<netdev@...r.kernel.org>, "Czapnik, Lukasz" <lukasz.czapnik@...el.com>, "Raj,
Victor" <victor.raj@...el.com>, "Nguyen, Anthony L"
<anthony.l.nguyen@...el.com>, "horms@...nel.org" <horms@...nel.org>,
"Kitszel, Przemyslaw" <przemyslaw.kitszel@...el.com>, "kuba@...nel.org"
<kuba@...nel.org>
Subject: RE: [Intel-wired-lan] [PATCH net-next v9 5/6] ice: Add
tx_scheduling_layers devlink param
> -----Original Message-----
> From: Intel-wired-lan <intel-wired-lan-bounces@...osl.org> On Behalf Of Mateusz Polchlopek
> Sent: Wednesday, April 3, 2024 1:11 PM
> To: intel-wired-lan@...ts.osuosl.org
> Cc: andrew@...n.ch; jiri@...nulli.us; Wilczynski, Michal <michal.wilczynski@...el.com>; Polchlopek, Mateusz <mateusz.polchlopek@...el.com>; netdev@...r.kernel.org; Czapnik, Lukasz <lukasz.czapnik@...el.com>; Raj, Victor <victor.raj@...el.com>; Nguyen, Anthony L <anthony.l.nguyen@...el.com>; horms@...nel.org; Kitszel, Przemyslaw <przemyslaw.kitszel@...el.com>; kuba@...nel.org
> Subject: [Intel-wired-lan] [PATCH net-next v9 5/6] ice: Add tx_scheduling_layers devlink param
>
> From: Lukasz Czapnik <lukasz.czapnik@...el.com>
>
> It was observed that Tx performance was inconsistent across all queues and/or VSIs and that it was directly connected to existing 9-layer topology of the Tx scheduler.
>
> Introduce new private devlink param - tx_scheduling_layers. This parameter gives user flexibility to choose the 5-layer transmit scheduler topology which helps to smooth out the transmit performance.
>
> Allowed parameter values are 5 and 9.
>
> Example usage:
>
> Show:
> devlink dev param show pci/0000:4b:00.0 name tx_scheduling_layers
> pci/0000:4b:00.0:
> name tx_scheduling_layers type driver-specific
> values:
> cmode permanent value 9
>
> Set:
> devlink dev param set pci/0000:4b:00.0 name tx_scheduling_layers value 5 cmode permanent
>
> devlink dev param set pci/0000:4b:00.0 name tx_scheduling_layers value 9 cmode permanent
>
> Signed-off-by: Lukasz Czapnik <lukasz.czapnik@...el.com>
> Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@...el.com>
> Co-developed-by: Mateusz Polchlopek <mateusz.polchlopek@...el.com>
> Signed-off-by: Mateusz Polchlopek <mateusz.polchlopek@...el.com>
> ---
> .../net/ethernet/intel/ice/devlink/devlink.c | 172 +++++++++++++++++-
> .../net/ethernet/intel/ice/ice_adminq_cmd.h | 9 +
> .../net/ethernet/intel/ice/ice_fw_update.c | 7 +-
> .../net/ethernet/intel/ice/ice_fw_update.h | 3 +
> drivers/net/ethernet/intel/ice/ice_nvm.c | 7 +-
> drivers/net/ethernet/intel/ice/ice_nvm.h | 3 +
> 6 files changed, 191 insertions(+), 10 deletions(-)
>
Tested-by: Pucha Himasekhar Reddy <himasekharx.reddy.pucha@...el.com> (A Contingent worker at Intel)
Powered by blists - more mailing lists