From: Mateusz Polchlopek <mateusz.polchlopek@intel.com>
To: intel-wired-lan@lists.osuosl.org
Cc: netdev@vger.kernel.org, kuba@kernel.org, jiri@resnulli.us,
horms@kernel.org, przemyslaw.kitszel@intel.com, andrew@lunn.ch,
victor.raj@intel.com, michal.wilczynski@intel.com,
lukasz.czapnik@intel.com,
Mateusz Polchlopek <mateusz.polchlopek@intel.com>
Subject: [Intel-wired-lan] [PATCH iwl-next v5 0/5] ice: Support 5 layer Tx scheduler topology
Date: Wed, 28 Feb 2024 09:20:49 -0500 [thread overview]
Message-ID: <20240228142054.474626-1-mateusz.polchlopek@intel.com> (raw)
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.
---
v5:
- updated Documentation commit as suggested in v4
v4:
- restored the initial way of passing firmware data to ice_cfg_tx_topo
function in ice_init_tx_topology function in ice_main.c file. In v2
and v3 version it was passed as const u8 parameter which caused kernel
crash. Because of this change I decided to drop all Reviewed-by tags.
https://lore.kernel.org/netdev/20240219100555.7220-1-mateusz.polchlopek@intel.com/
v3:
- fixed documentation warnings
https://lore.kernel.org/netdev/20231009090711.136777-1-mateusz.polchlopek@intel.com/
v2:
- updated documentation
- reorder of variables list (default-init first)
- comments changed to be more descriptive
- added elseif's instead of few if's
- returned error when ice_request_fw fails
- ice_cfg_tx_topo() changed to take const u8 as parameter (get rid of copy
buffer)
- renamed all "balance" occurences to the new one
- prevent fail of ice_aq_read_nvm() function
- unified variables names (int err instead of int status in few
functions)
- some smaller fixes, typo fixes
https://lore.kernel.org/netdev/20231006110212.96305-1-mateusz.polchlopek@intel.com/
v1:
https://lore.kernel.org/netdev/20230523174008.3585300-1-anthony.l.nguyen@intel.com/
---
Lukasz Czapnik (1):
ice: Add tx_scheduling_layers devlink param
Michal Wilczynski (2):
ice: Enable switching default Tx scheduler topology
ice: Document tx_scheduling_layers parameter
Raj Victor (2):
ice: Support 5 layer topology
ice: Adjust the VSI/Aggregator layers
Documentation/networking/devlink/ice.rst | 47 +++++
.../net/ethernet/intel/ice/ice_adminq_cmd.h | 31 +++
drivers/net/ethernet/intel/ice/ice_common.c | 5 +
drivers/net/ethernet/intel/ice/ice_ddp.c | 199 ++++++++++++++++++
drivers/net/ethernet/intel/ice/ice_ddp.h | 2 +
drivers/net/ethernet/intel/ice/ice_devlink.c | 169 +++++++++++++++
.../net/ethernet/intel/ice/ice_fw_update.c | 7 +-
.../net/ethernet/intel/ice/ice_fw_update.h | 3 +
drivers/net/ethernet/intel/ice/ice_main.c | 102 +++++++--
drivers/net/ethernet/intel/ice/ice_nvm.c | 7 +-
drivers/net/ethernet/intel/ice/ice_nvm.h | 3 +
drivers/net/ethernet/intel/ice/ice_sched.c | 37 ++--
drivers/net/ethernet/intel/ice/ice_sched.h | 3 +
drivers/net/ethernet/intel/ice/ice_type.h | 1 +
14 files changed, 571 insertions(+), 45 deletions(-)
--
2.38.1
next reply other threads:[~2024-02-28 14:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 14:20 Mateusz Polchlopek [this message]
2024-02-28 14:20 ` [Intel-wired-lan] [PATCH iwl-next v5 1/5] ice: Support 5 layer topology Mateusz Polchlopek
2024-02-28 14:20 ` [Intel-wired-lan] [PATCH iwl-next v5 2/5] ice: Adjust the VSI/Aggregator layers Mateusz Polchlopek
2024-02-28 14:20 ` [Intel-wired-lan] [PATCH iwl-next v5 3/5] ice: Enable switching default Tx scheduler topology Mateusz Polchlopek
2024-02-28 14:20 ` [Intel-wired-lan] [PATCH iwl-next v5 4/5] ice: Add tx_scheduling_layers devlink param Mateusz Polchlopek
2024-02-28 15:57 ` Jiri Pirko
2024-03-01 13:41 ` Mateusz Polchlopek
2024-03-01 15:46 ` Jiri Pirko
2024-03-05 12:31 ` Mateusz Polchlopek
2024-02-28 14:20 ` [Intel-wired-lan] [PATCH iwl-next v5 5/5] ice: Document tx_scheduling_layers parameter Mateusz Polchlopek
2024-03-05 3:35 ` Jakub Kicinski
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=20240228142054.474626-1-mateusz.polchlopek@intel.com \
--to=mateusz.polchlopek@intel.com \
--cc=andrew@lunn.ch \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=lukasz.czapnik@intel.com \
--cc=michal.wilczynski@intel.com \
--cc=netdev@vger.kernel.org \
--cc=przemyslaw.kitszel@intel.com \
--cc=victor.raj@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;
as well as URLs for NNTP newsgroup(s).