From: Jakub Kicinski <kuba@kernel.org>
To: Gal Pressman <gal@nvidia.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
ecree.xilinx@gmail.com
Subject: Re: [PATCH net-next 0/9] net: ethtool: add dedicated RXFH driver callbacks
Date: Wed, 25 Jun 2025 13:17:02 -0700 [thread overview]
Message-ID: <20250625131702.173bd5ee@kernel.org> (raw)
In-Reply-To: <db9f1187-a994-49e8-a05a-58322a317102@nvidia.com>
On Wed, 25 Jun 2025 09:44:04 +0300 Gal Pressman wrote:
> On 11/06/2025 17:59, Jakub Kicinski wrote:
> > The future of n-tuple filters is uncertain within netlink.
>
> What does that mean exactly?
Just that I don't have a clear idea of where it should go.
In this series I was refactoring rxnfc code - one could argue
I should also add dedicated callbacks for n-tuple ioctls
which are also muxed into the rxnfc driver op. But at some
point some people were pushing for n-tuple filters to be
deprecated in favor of cls_flower. Also Jamal's P4-ish
proposal could become n-tuple-next-gen. Or we could lift
existing ntuple filters into netlink.. 🤷️
IDK where we are on that, so I'm not refactoring the ntuple callbacks.
prev parent reply other threads:[~2025-06-25 20:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 14:59 [PATCH net-next 0/9] net: ethtool: add dedicated RXFH driver callbacks Jakub Kicinski
2025-06-11 14:59 ` [PATCH net-next 1/9] net: ethtool: copy the rxfh flow handling Jakub Kicinski
2025-06-12 21:02 ` Joe Damato
2025-06-11 14:59 ` [PATCH net-next 2/9] net: ethtool: remove the duplicated handling from rxfh and rxnfc Jakub Kicinski
2025-06-12 21:34 ` Joe Damato
2025-06-11 14:59 ` [PATCH net-next 3/9] net: ethtool: require drivers to opt into the per-RSS ctx RXFH Jakub Kicinski
2025-06-12 21:09 ` Joe Damato
2025-06-11 14:59 ` [PATCH net-next 4/9] net: ethtool: add dedicated callbacks for getting and setting rxfh fields Jakub Kicinski
2025-06-13 5:36 ` Joe Damato
2025-06-13 14:39 ` Jakub Kicinski
2025-06-11 14:59 ` [PATCH net-next 5/9] eth: remove empty RXFH handling from drivers Jakub Kicinski
2025-06-12 3:21 ` Ziwei Xiao
2025-06-11 14:59 ` [PATCH net-next 6/9] eth: fbnic: migrate to new RXFH callbacks Jakub Kicinski
2025-06-11 14:59 ` [PATCH net-next 7/9] net: drv: vmxnet3: " Jakub Kicinski
2025-06-11 14:59 ` [PATCH net-next 8/9] net: drv: virtio: " Jakub Kicinski
2025-06-13 0:42 ` Jason Wang
2025-06-11 14:59 ` [PATCH net-next 9/9] net: drv: hyperv: " Jakub Kicinski
2025-06-13 0:50 ` [PATCH net-next 0/9] net: ethtool: add dedicated RXFH driver callbacks patchwork-bot+netdevbpf
2025-06-25 6:44 ` Gal Pressman
2025-06-25 20:17 ` Jakub Kicinski [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=20250625131702.173bd5ee@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=horms@kernel.org \
--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 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).