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,
marcin.szycik@linux.intel.com
Subject: Re: [PATCH net-next 0/7][pull request] ice: Switch API optimizations
Date: Sun, 14 Jul 2024 14:50:31 +0000 [thread overview]
Message-ID: <172096863173.6543.16540997870486665772.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240711181312.2019606-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 Thu, 11 Jul 2024 11:13:03 -0700 you wrote:
> Marcin Szycik says:
>
> Optimize the process of creating a recipe in the switch block by removing
> duplicate switch ID words and changing how result indexes are fitted into
> recipes. In many cases this can decrease the number of recipes required to
> add a certain set of rules, potentially allowing a more varied set of rules
> to be created. Total rule count will also increase, since less words will
> be left unused/wasted. There are only 64 rules available in total, so every
> one counts.
>
> [...]
Here is the summary with links:
- [net-next,1/7] ice: Remove unused struct ice_prot_lkup_ext members
https://git.kernel.org/netdev/net-next/c/e247267bbeaf
- [net-next,2/7] ice: Remove reading all recipes before adding a new one
https://git.kernel.org/netdev/net-next/c/c563908494e9
- [net-next,3/7] ice: Simplify bitmap setting in adding recipe
https://git.kernel.org/netdev/net-next/c/3125eb559590
- [net-next,4/7] ice: remove unused recipe bookkeeping data
https://git.kernel.org/netdev/net-next/c/589dd7145a8e
- [net-next,5/7] ice: Optimize switch recipe creation
https://git.kernel.org/netdev/net-next/c/2ecdd4ba47fc
- [net-next,6/7] ice: Remove unused members from switch API
https://git.kernel.org/netdev/net-next/c/1d2ac128531e
- [net-next,7/7] ice: Add tracepoint for adding and removing switch rules
https://git.kernel.org/netdev/net-next/c/e10989e56f52
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-07-14 14:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-11 18:13 [PATCH net-next 0/7][pull request] ice: Switch API optimizations Tony Nguyen
2024-07-11 18:13 ` [PATCH net-next 1/7] ice: Remove unused struct ice_prot_lkup_ext members Tony Nguyen
2024-07-11 18:13 ` [PATCH net-next 2/7] ice: Remove reading all recipes before adding a new one Tony Nguyen
2024-07-11 18:13 ` [PATCH net-next 3/7] ice: Simplify bitmap setting in adding recipe Tony Nguyen
2024-07-11 18:13 ` [PATCH net-next 4/7] ice: remove unused recipe bookkeeping data Tony Nguyen
2024-07-11 18:13 ` [PATCH net-next 5/7] ice: Optimize switch recipe creation Tony Nguyen
2024-07-11 18:13 ` [PATCH net-next 6/7] ice: Remove unused members from switch API Tony Nguyen
2024-07-11 18:13 ` [PATCH net-next 7/7] ice: Add tracepoint for adding and removing switch rules Tony Nguyen
2024-07-14 14:50 ` 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=172096863173.6543.16540997870486665772.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=marcin.szycik@linux.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.