From: Paolo Abeni <pabeni@redhat.com>
To: Andrii Staikov <andrii.staikov@intel.com>,
intel-wired-lan@lists.osuosl.org
Cc: netdev@vger.kernel.org
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v2] ice: Add support for packet mirroring using hardware in switchdev mode
Date: Tue, 12 Sep 2023 11:56:15 +0200 [thread overview]
Message-ID: <0168a988486f4bff08bd186d5aea1cfe4900a2c3.camel@redhat.com> (raw)
In-Reply-To: <20230912092952.2814966-1-andrii.staikov@intel.com>
Hi all,
On Tue, 2023-09-12 at 11:29 +0200, Andrii Staikov wrote:
> Switchdev mode allows to add mirroring rules to mirror
> incoming and outgoing packets to the interface's port
> representor. Previously, this was available only using
> software functionality. Add possibility to offload this
> functionality to the NIC hardware.
>
> Introduce ICE_MIRROR_PACKET filter action to the
> ice_sw_fwd_act_type enum to identify the desired action
> and pass it to the hardware as well as the VSI to mirror.
>
> Example of tc mirror command using hardware:
> tc filter add dev ens1f0np0 ingress protocol ip prio 1 flower
> src_mac b4:96:91:a5:c7:a7 skip_sw action mirred egress mirror dev eth1
>
> ens1f0np0 - PF
> b4:96:91:a5:c7:a7 - source MAC address
> eth1 - PR of a VF to mirror to
>
> Signed-off-by: Andrii Staikov <andrii.staikov@intel.com>
The amount of patches that IMHO should land only into intel-specific
MLs and instead reaches also netdev, recently increased.
Please try harder to apply proper constraints to your traffic, netdev
is already busy enough!
Thanks,
Paolo
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next prev parent reply other threads:[~2023-09-12 9:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 9:29 [Intel-wired-lan] [PATCH iwl-next v2] ice: Add support for packet mirroring using hardware in switchdev mode Andrii Staikov
2023-09-12 9:56 ` Paolo Abeni [this message]
2023-09-12 14:41 ` Alexander Lobakin
2023-09-12 16:43 ` Paolo Abeni
2023-10-03 7:49 ` Buvaneswaran, Sujai
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=0168a988486f4bff08bd186d5aea1cfe4900a2c3.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=andrii.staikov@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=netdev@vger.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