From: patchwork-bot+netdevbpf@kernel.org
To: <edward.cree@amd.com>
Cc: davem@davemloft.net, kuba@kernel.org, edumazet@google.com,
pabeni@redhat.com, ecree.xilinx@gmail.com,
netdev@vger.kernel.org, horms@kernel.org, andrew+netdev@lunn.ch,
shuah@kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next 0/5] net: make RSS+RXNFC semantics more explicit
Date: Fri, 15 Nov 2024 04:40:33 +0000 [thread overview]
Message-ID: <173164563325.2151510.15712104184262372756.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1731499021.git.ecree.xilinx@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 13 Nov 2024 12:13:08 +0000 you wrote:
> From: Edward Cree <ecree.xilinx@gmail.com>
>
> The original semantics of ntuple filters with FLOW_RSS were not
> fully understood by all drivers, some ignoring the ring_cookie from
> the flow rule. Require this support to be explicitly declared by
> the driver for filters relying on it to be inserted, and add self-
> test coverage for this functionality.
> Also teach ethtool_check_max_channel() about this.
>
> [...]
Here is the summary with links:
- [net-next,1/5] net: ethtool: only allow set_rxnfc with rss + ring_cookie if driver opts in
https://git.kernel.org/netdev/net-next/c/9e43ad7a1ede
- [net-next,2/5] net: ethtool: account for RSS+RXNFC add semantics when checking channel count
https://git.kernel.org/netdev/net-next/c/a64499f618b2
- [net-next,3/5] selftest: include dst-ip in ethtool ntuple rules
https://git.kernel.org/netdev/net-next/c/b2d5b4c46856
- [net-next,4/5] selftest: validate RSS+ntuple filters with nonzero ring_cookie
https://git.kernel.org/netdev/net-next/c/e9e8abfec214
- [net-next,5/5] selftest: extend test_rss_context_queue_reconfigure for action addition
https://git.kernel.org/netdev/net-next/c/29a4bc1fe961
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-11-15 4:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-13 12:13 [PATCH net-next 0/5] net: make RSS+RXNFC semantics more explicit edward.cree
2024-11-13 12:13 ` [PATCH net-next 1/5] net: ethtool: only allow set_rxnfc with rss + ring_cookie if driver opts in edward.cree
2024-11-14 9:21 ` Martin Habets
2024-11-25 7:11 ` Gal Pressman
2024-11-25 13:21 ` Edward Cree
2024-11-25 14:10 ` Gal Pressman
2024-11-25 14:20 ` Ahmed Zaki
2024-11-25 14:26 ` Gal Pressman
2024-11-25 14:42 ` Edward Cree
2024-11-25 19:01 ` Ahmed Zaki
2024-12-02 15:19 ` Ahmed Zaki
2024-11-25 18:13 ` Edward Cree
2024-11-13 12:13 ` [PATCH net-next 2/5] net: ethtool: account for RSS+RXNFC add semantics when checking channel count edward.cree
2024-11-13 12:13 ` [PATCH net-next 3/5] selftest: include dst-ip in ethtool ntuple rules edward.cree
2024-11-14 9:54 ` Martin Habets
2024-11-13 12:13 ` [PATCH net-next 4/5] selftest: validate RSS+ntuple filters with nonzero ring_cookie edward.cree
2024-11-13 12:13 ` [PATCH net-next 5/5] selftest: extend test_rss_context_queue_reconfigure for action addition edward.cree
2024-11-15 4:40 ` 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=173164563325.2151510.15712104184262372756.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=edward.cree@amd.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox