From: Simon Horman <horms@kernel.org>
To: Ahmed Zaki <ahmed.zaki@intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
sridhar.samudrala@intel.com, aleksandr.loktionov@intel.com,
aleksander.lobakin@intel.com, dinesh.kumar@intel.com,
anthony.l.nguyen@intel.com, przemyslaw.kitszel@intel.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, almasrymina@google.com,
willemb@google.com, pmenzel@molgen.mpg.de
Subject: Re: [PATCH iwl-next v5 3/3] idpf: add flow steering support
Date: Fri, 16 May 2025 09:54:48 +0100 [thread overview]
Message-ID: <20250516085448.GE1898636@horms.kernel.org> (raw)
In-Reply-To: <20250423192705.1648119-4-ahmed.zaki@intel.com>
On Wed, Apr 23, 2025 at 01:27:05PM -0600, Ahmed Zaki wrote:
> Use the new virtchnl2 OP codes to communicate with the Control Plane to
> add flow steering filters. We add the basic functionality for add/delete
> with TCP/UDP IPv4 only. Support for other OP codes and protocols will be
> added later.
>
> Standard 'ethtool -N|--config-ntuple' should be used, for example:
>
> # ethtool -N ens801f0d1 flow-type tcp4 src-ip 10.0.0.1 action 6
>
> to route all IPv4/TCP traffic from IP 10.0.0.1 to queue 6.
>
> Reviewed-by: Sridhar Samudrala <sridhar.samudrala@intel.com>
> Signed-off-by: Ahmed Zaki <ahmed.zaki@intel.com>
Reviewed-by: Simon Horman <horms@kernel.org>
prev parent reply other threads:[~2025-05-16 8:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 19:27 [PATCH iwl-next v5 0/3] idpf: add flow steering support Ahmed Zaki
2025-04-23 19:27 ` [PATCH iwl-next v5 1/3] virtchnl2: rename enum virtchnl2_cap_rss Ahmed Zaki
2025-05-16 8:54 ` Simon Horman
2025-04-23 19:27 ` [PATCH iwl-next v5 2/3] virtchnl2: add flow steering support Ahmed Zaki
2025-05-16 8:54 ` Simon Horman
2025-04-23 19:27 ` [PATCH iwl-next v5 3/3] idpf: " Ahmed Zaki
2025-05-16 8:54 ` Simon Horman [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=20250516085448.GE1898636@horms.kernel.org \
--to=horms@kernel.org \
--cc=ahmed.zaki@intel.com \
--cc=aleksander.lobakin@intel.com \
--cc=aleksandr.loktionov@intel.com \
--cc=almasrymina@google.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=dinesh.kumar@intel.com \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pmenzel@molgen.mpg.de \
--cc=przemyslaw.kitszel@intel.com \
--cc=sridhar.samudrala@intel.com \
--cc=willemb@google.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).