public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	edumazet@google.com, netdev@vger.kernel.org,
	michal.wilczynski@intel.com, lukasz.czapnik@intel.com,
	przemyslaw.kitszel@intel.com
Subject: Re: [PATCH net-next 0/5][pull request] ice: Support 5 layer Tx scheduler topology
Date: Wed, 24 May 2023 13:54:23 +0200	[thread overview]
Message-ID: <ZG367+pNuYtvHXPh@nanopsycho> (raw)
In-Reply-To: <20230523174008.3585300-1-anthony.l.nguyen@intel.com>

Tue, May 23, 2023 at 07:40:03PM CEST, anthony.l.nguyen@intel.com wrote:
>Michal Wilczynski says:
>
>For performance reasons there is a need to have support for selectable
>Tx scheduler topology. Currently firmware supports only the default
>9-layer and 5-layer topology. This patch series enables switch from
>default to 5-layer topology, if user decides to opt-in.

Why exactly the user cares which FW implementation you use. From what I
see, there is a FW but causing unequal queue distribution in some cases,
you fox this. Why would the user want to alter the behaviour between
fixed and unfixed?


>
>The following are changes since commit b2e3406a38f0f48b1dfb81e5bb73d243ff6af179:
>  octeontx2-pf: Add support for page pool
>and are available in the git repository at:
>  git://git.kernel.org/pub/scm/linux/kernel/git/tnguy/next-queue 100GbE
>
>Lukasz Czapnik (1):
>  ice: Add txbalancing devlink param
>
>Michal Wilczynski (2):
>  ice: Enable switching default tx scheduler topology
>  ice: Document txbalancing parameter
>
>Raj Victor (2):
>  ice: Support 5 layer topology
>  ice: Adjust the VSI/Aggregator layers
>
> Documentation/networking/devlink/ice.rst      |  17 ++
> .../net/ethernet/intel/ice/ice_adminq_cmd.h   |  31 +++
> drivers/net/ethernet/intel/ice/ice_common.c   |   6 +
> drivers/net/ethernet/intel/ice/ice_ddp.c      | 200 ++++++++++++++++++
> drivers/net/ethernet/intel/ice/ice_ddp.h      |   7 +-
> drivers/net/ethernet/intel/ice/ice_devlink.c  | 161 +++++++++++++-
> .../net/ethernet/intel/ice/ice_fw_update.c    |   2 +-
> .../net/ethernet/intel/ice/ice_fw_update.h    |   3 +
> drivers/net/ethernet/intel/ice/ice_main.c     | 105 +++++++--
> drivers/net/ethernet/intel/ice/ice_nvm.c      |   2 +-
> drivers/net/ethernet/intel/ice/ice_nvm.h      |   3 +
> drivers/net/ethernet/intel/ice/ice_sched.c    |  34 +--
> drivers/net/ethernet/intel/ice/ice_sched.h    |   3 +
> drivers/net/ethernet/intel/ice/ice_type.h     |   1 +
> 14 files changed, 534 insertions(+), 41 deletions(-)
>
>-- 
>2.38.1
>

  parent reply	other threads:[~2023-05-24 11:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-23 17:40 [PATCH net-next 0/5][pull request] ice: Support 5 layer Tx scheduler topology Tony Nguyen
2023-05-23 17:40 ` [PATCH net-next 1/5] ice: Support 5 layer topology Tony Nguyen
2023-05-23 17:40 ` [PATCH net-next 2/5] ice: Adjust the VSI/Aggregator layers Tony Nguyen
2023-05-23 17:40 ` [PATCH net-next 3/5] ice: Enable switching default tx scheduler topology Tony Nguyen
2023-05-23 17:40 ` [PATCH net-next 4/5] ice: Add txbalancing devlink param Tony Nguyen
2023-05-24 11:57   ` Jiri Pirko
2023-05-25 16:01     ` Lukasz Czapnik
2023-05-23 17:40 ` [PATCH net-next 5/5] ice: Document txbalancing parameter Tony Nguyen
2023-05-24 11:54 ` Jiri Pirko [this message]
2023-05-24 13:25   ` [PATCH net-next 0/5][pull request] ice: Support 5 layer Tx scheduler topology Wilczynski, Michal
2023-05-24 16:26     ` Jakub Kicinski
2023-05-24 16:59       ` Wilczynski, Michal
2023-05-24 20:02         ` Jakub Kicinski
2023-05-25  7:49           ` Wilczynski, Michal
2023-05-25 15:41             ` Jakub Kicinski
2023-05-26  7:43               ` Wilczynski, Michal

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=ZG367+pNuYtvHXPh@nanopsycho \
    --to=jiri@resnulli.us \
    --cc=anthony.l.nguyen@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=lukasz.czapnik@intel.com \
    --cc=michal.wilczynski@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=przemyslaw.kitszel@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