All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Mateusz Polchlopek <mateusz.polchlopek@intel.com>
Cc: netdev@vger.kernel.org, intel-wired-lan@lists.osuosl.org
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v3 0/5] ice: Support 5 layer Tx scheduler topology
Date: Mon, 16 Oct 2023 10:56:16 +0200	[thread overview]
Message-ID: <20231016085616.GF1501712@kernel.org> (raw)
In-Reply-To: <20231009090711.136777-1-mateusz.polchlopek@intel.com>

On Mon, Oct 09, 2023 at 05:07:06AM -0400, Mateusz Polchlopek wrote:
> 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.
> 
> ---
> v3:
> - fixed documentation warnings
> 
> 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

For series,

Reviewed-by: Simon Horman <horms@kernel.org>

_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

WARNING: multiple messages have this Message-ID (diff)
From: Simon Horman <horms@kernel.org>
To: Mateusz Polchlopek <mateusz.polchlopek@intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v3 0/5] ice: Support 5 layer Tx scheduler topology
Date: Mon, 16 Oct 2023 10:56:16 +0200	[thread overview]
Message-ID: <20231016085616.GF1501712@kernel.org> (raw)
In-Reply-To: <20231009090711.136777-1-mateusz.polchlopek@intel.com>

On Mon, Oct 09, 2023 at 05:07:06AM -0400, Mateusz Polchlopek wrote:
> 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.
> 
> ---
> v3:
> - fixed documentation warnings
> 
> 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

For series,

Reviewed-by: Simon Horman <horms@kernel.org>


  parent reply	other threads:[~2023-10-16  8:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-09  9:07 [Intel-wired-lan] [PATCH iwl-next v3 0/5] ice: Support 5 layer Tx scheduler topology Mateusz Polchlopek
2023-10-09  9:07 ` Mateusz Polchlopek
2023-10-09  9:07 ` [Intel-wired-lan] [PATCH iwl-next v3 1/5] ice: Support 5 layer topology Mateusz Polchlopek
2023-10-09  9:07   ` Mateusz Polchlopek
2023-10-09  9:07 ` [Intel-wired-lan] [PATCH iwl-next v3 2/5] ice: Adjust the VSI/Aggregator layers Mateusz Polchlopek
2023-10-09  9:07   ` Mateusz Polchlopek
2023-10-09  9:07 ` [Intel-wired-lan] [PATCH iwl-next v3 3/5] ice: Enable switching default Tx scheduler topology Mateusz Polchlopek
2023-10-09  9:07   ` Mateusz Polchlopek
2023-10-09  9:07 ` [Intel-wired-lan] [PATCH iwl-next v3 4/5] ice: Add tx_scheduling_layers devlink param Mateusz Polchlopek
2023-10-09  9:07   ` Mateusz Polchlopek
2023-10-09  9:07 ` [Intel-wired-lan] [PATCH iwl-next v3 5/5] ice: Document tx_scheduling_layers parameter Mateusz Polchlopek
2023-10-09  9:07   ` Mateusz Polchlopek
2023-10-16  8:56 ` Simon Horman [this message]
2023-10-16  8:56   ` [Intel-wired-lan] [PATCH iwl-next v3 0/5] ice: Support 5 layer Tx scheduler topology Simon Horman

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=20231016085616.GF1501712@kernel.org \
    --to=horms@kernel.org \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=mateusz.polchlopek@intel.com \
    --cc=netdev@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.