From: "G, GurucharanX" <gurucharanx.g@intel.com>
To: "Wilczynski, Michal" <michal.wilczynski@intel.com>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>
Cc: "Wilczynski, Michal" <michal.wilczynski@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH net-next v8 4/5] ice: Add txbalancing devlink param
Date: Tue, 26 Jul 2022 06:52:35 +0000 [thread overview]
Message-ID: <BYAPR11MB336780BA81F328257CB65331FC949@BYAPR11MB3367.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220722141129.229436-5-michal.wilczynski@intel.com>
> -----Original Message-----
> From: Intel-wired-lan <intel-wired-lan-bounces@osuosl.org> On Behalf Of
> Michal Wilczynski
> Sent: Friday, July 22, 2022 7:41 PM
> To: intel-wired-lan@lists.osuosl.org
> Cc: Wilczynski, Michal <michal.wilczynski@intel.com>
> Subject: [Intel-wired-lan] [PATCH net-next v8 4/5] ice: Add txbalancing
> devlink param
>
> From: Lukasz Czapnik <lukasz.czapnik@intel.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 - txbalance. 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 true for enabled and false for disabled.
>
> Example usage:
>
> Show:
> devlink dev param show pci/0000:4b:00.0 name txbalancing
> pci/0000:4b:00.0:
> name txbalancing type driver-specific
> values:
> cmode permanent value true
>
> Set:
> devlink dev param set pci/0000:4b:00.0 name txbalancing value true cmode
> permanent
>
> Signed-off-by: Lukasz Czapnik <lukasz.czapnik@intel.com>
> Signed-off-by: Michal Wilczynski <michal.wilczynski@intel.com>
> ---
> .../net/ethernet/intel/ice/ice_adminq_cmd.h | 9 +
> drivers/net/ethernet/intel/ice/ice_devlink.c | 161 ++++++++++++++++++
> .../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 | 2 +-
> drivers/net/ethernet/intel/ice/ice_nvm.h | 4 +
> 6 files changed, 181 insertions(+), 5 deletions(-)
>
Tested-by: Gurucharan <gurucharanx.g@intel.com> (A Contingent worker at Intel)
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next prev parent reply other threads:[~2022-07-26 6:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 14:11 [Intel-wired-lan] [PATCH net-next v8 0/5] ice: Support 5 layer tx scheduler topology Michal Wilczynski
2022-07-22 14:11 ` [Intel-wired-lan] [PATCH net-next v8 1/5] ice: Support 5 layer topology Michal Wilczynski
2022-07-27 6:32 ` G, GurucharanX
2022-07-22 14:11 ` [Intel-wired-lan] [PATCH net-next v8 2/5] ice: Adjust the VSI/Aggregator layers Michal Wilczynski
2022-07-22 14:11 ` [Intel-wired-lan] [PATCH net-next v8 3/5] ice: Enable switching default tx scheduler topology Michal Wilczynski
2022-07-26 7:39 ` G, GurucharanX
2022-07-22 14:11 ` [Intel-wired-lan] [PATCH net-next v8 4/5] ice: Add txbalancing devlink param Michal Wilczynski
2022-07-26 6:52 ` G, GurucharanX [this message]
2022-07-22 14:11 ` [Intel-wired-lan] [PATCH net-next v8 5/5] ice: Document txbalancing parameter Michal Wilczynski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BYAPR11MB336780BA81F328257CB65331FC949@BYAPR11MB3367.namprd11.prod.outlook.com \
--to=gurucharanx.g@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=michal.wilczynski@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox