From: Jacob Keller <jacob.e.keller@intel.com>
To: <intel-wired-lan@osuosl.org>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v7 2/2] ice: Implement 'flow-type ether' rules
Date: Wed, 14 Feb 2024 15:50:23 -0800 [thread overview]
Message-ID: <8733caf1-c35c-4600-b16b-750f1df95129@intel.com> (raw)
In-Reply-To: <20240212110307.12704-3-lukasz.plachno@intel.com>
On 2/12/2024 3:03 AM, Lukasz Plachno wrote:
> From: Jakub Buchocki <jakubx.buchocki@intel.com>
>
> Add support for 'flow-type ether' Flow Director rules via ethtool.
>
> Create packet segment info for filter configuration based on ethtool
> command parameters. Reuse infrastructure already created for
> ipv4 and ipv6 flows to convert packet segment into
> extraction sequence, which is later used to program the filter
> inside Flow Director block of the Rx pipeline.
>
> Rules not containing masks are processed by the Flow Director,
> and support the following set of input parameters in all combinations:
> src, dst, proto, vlan-etype, vlan, action.
>
> It is possible to specify address mask in ethtool parameters but only
> 00:00:00:00:00 and FF:FF:FF:FF:FF are valid.
> The same applies to proto, vlan-etype and vlan masks:
> only 0x0000 and 0xffff masks are valid.
>
> Testing:
> (DUT) iperf3 -s
> (DUT) ethtool -U ens785f0np0 flow-type ether dst <ens785f0np0 mac> \
> action 10
> (DUT) watch 'ethtool -S ens785f0np0 | grep rx_queue'
> (LP) iperf3 -c ${DUT_IP}
>
> Counters increase only for:
> 'rx_queue_10_packets'
> 'rx_queue_10_bytes'
>
> Signed-off-by: Jakub Buchocki <jakubx.buchocki@intel.com>
> Co-developed-by: Mateusz Pacuszka <mateuszx.pacuszka@intel.com>
> Signed-off-by: Mateusz Pacuszka <mateuszx.pacuszka@intel.com>
> Signed-off-by: Lukasz Plachno <lukasz.plachno@intel.com>
Reviewed-by: Jacob Keller <jacob.e.keller@intel.com>
next prev parent reply other threads:[~2024-02-14 23:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 11:03 [Intel-wired-lan] [PATCH iwl-next v7 0/2] ice: Support flow director ether type filters Lukasz Plachno
2024-02-12 11:03 ` [Intel-wired-lan] [PATCH iwl-next v7 1/2] ice: Remove unnecessary argument from ice_fdir_comp_rules() Lukasz Plachno
2024-02-14 23:42 ` Jacob Keller
2024-02-12 11:03 ` [Intel-wired-lan] [PATCH iwl-next v7 2/2] ice: Implement 'flow-type ether' rules Lukasz Plachno
2024-02-14 23:47 ` Jacob Keller
2024-02-14 23:50 ` Jacob Keller [this message]
2024-02-29 11:59 ` Plachno, Lukasz
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=8733caf1-c35c-4600-b16b-750f1df95129@intel.com \
--to=jacob.e.keller@intel.com \
--cc=intel-wired-lan@osuosl.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