From: Jakub Kicinski <kuba@kernel.org>
To: Geetha sowjanya <gakula@marvell.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<davem@davemloft.net>, <pabeni@redhat.com>, <edumazet@google.com>,
<sgoutham@marvell.com>, <sbhatta@marvell.com>,
<hkelam@marvell.com>
Subject: Re: [net-next v2 PATCH] octeontx2-pf: TC flower offload support for ICMP type and code
Date: Wed, 1 Nov 2023 21:42:23 -0700 [thread overview]
Message-ID: <20231101214223.0de10cdb@kernel.org> (raw)
In-Reply-To: <20231031165258.30002-1-gakula@marvell.com>
On Tue, 31 Oct 2023 22:22:58 +0530 Geetha sowjanya wrote:
> Adds tc offload support for matching on ICMP type and code.
>
> Example usage:
> To enable adding tc ingress rules
> tc qdisc add dev eth0 ingress
>
> TC rule drop the ICMP echo reply:
> tc filter add dev eth0 protocol ip parent ffff: \
> flower ip_proto icmp type 8 code 0 skip_sw action drop
>
> TC rule to drop ICMPv6 echo reply:
> tc filter add dev eth0 protocol ipv6 parent ffff: flower \
> indev eth0 ip_proto icmpv6 type 128 code 0 action drop
## Form letter - net-next-closed
The merge window for v6.7 has begun and we have already posted our pull
request. Therefore net-next is closed for new drivers, features, code
refactoring and optimizations. We are currently accepting bug fixes only.
Please repost when net-next reopens after Nov 12th.
RFC patches sent for review only are obviously welcome at any time.
See: https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#development-cycle
--
pw-bot: defer
prev parent reply other threads:[~2023-11-02 4:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 16:52 [net-next v2 PATCH] octeontx2-pf: TC flower offload support for ICMP type and code Geetha sowjanya
2023-11-02 4:42 ` 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=20231101214223.0de10cdb@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.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).