All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
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,
	mateusz.polchlopek@intel.com
Subject: Re: [PATCH net-next 0/6][pull request] ice: Support 5 layer Tx scheduler topology
Date: Thu, 25 Apr 2024 03:10:28 +0000	[thread overview]
Message-ID: <171401462833.4490.1421617944754978587.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240422203913.225151-1-anthony.l.nguyen@intel.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Tony Nguyen <anthony.l.nguyen@intel.com>:

On Mon, 22 Apr 2024 13:39:05 -0700 you wrote:
> Mateusz Polchlopek 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.
> 
> [...]

Here is the summary with links:
  - [net-next,1/6] devlink: extend devlink_param *set pointer
    https://git.kernel.org/netdev/net-next/c/5625ca5640ca
  - [net-next,2/6] ice: Support 5 layer topology
    https://git.kernel.org/netdev/net-next/c/91427e6d9030
  - [net-next,3/6] ice: Adjust the VSI/Aggregator layers
    https://git.kernel.org/netdev/net-next/c/927127cda11a
  - [net-next,4/6] ice: Enable switching default Tx scheduler topology
    https://git.kernel.org/netdev/net-next/c/cc5776fe1832
  - [net-next,5/6] ice: Add tx_scheduling_layers devlink param
    https://git.kernel.org/netdev/net-next/c/109eb2917284
  - [net-next,6/6] ice: Document tx_scheduling_layers parameter
    https://git.kernel.org/netdev/net-next/c/9afff0de30db

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-04-25  3:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-22 20:39 [PATCH net-next 0/6][pull request] ice: Support 5 layer Tx scheduler topology Tony Nguyen
2024-04-22 20:39 ` [PATCH net-next 1/6] devlink: extend devlink_param *set pointer Tony Nguyen
2024-04-24  9:05   ` Alexander Lobakin
2024-04-24  9:20     ` Przemek Kitszel
2024-04-24  9:24       ` Alexander Lobakin
2024-04-24  9:40         ` Przemek Kitszel
2024-04-24  9:52         ` Mateusz Polchlopek
2024-04-25  3:08     ` Jakub Kicinski
2024-04-22 20:39 ` [PATCH net-next 2/6] ice: Support 5 layer topology Tony Nguyen
2024-04-22 20:39 ` [PATCH net-next 3/6] ice: Adjust the VSI/Aggregator layers Tony Nguyen
2024-04-22 20:39 ` [PATCH net-next 4/6] ice: Enable switching default Tx scheduler topology Tony Nguyen
2024-04-22 20:39 ` [PATCH net-next 5/6] ice: Add tx_scheduling_layers devlink param Tony Nguyen
2024-04-22 20:39 ` [PATCH net-next 6/6] ice: Document tx_scheduling_layers parameter Tony Nguyen
2024-04-23 12:37   ` Bagas Sanjaya
2024-04-24  9:54     ` Mateusz Polchlopek
2024-04-24 10:47       ` Bagas Sanjaya
2024-04-25  3:10 ` patchwork-bot+netdevbpf [this message]

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=171401462833.4490.1421617944754978587.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=anthony.l.nguyen@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=mateusz.polchlopek@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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 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.