From: Ido Schimmel <idosch@idosch.org>
To: Zahari Doychev <zahari.doychev@linux.com>
Cc: netdev@vger.kernel.org, jhs@mojatatu.com,
xiyou.wangcong@gmail.com, jiri@resnulli.us, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
hmehrtens@maxlinear.com, aleksander.lobakin@intel.com,
simon.horman@corigine.com,
Zahari Doychev <zdoychev@maxlinear.com>
Subject: Re: [PATCH net-next v7 2/3] net: flower: add support for matching cfm fields
Date: Thu, 8 Jun 2023 15:27:25 +0300 [thread overview]
Message-ID: <ZIHJLW71NjbuPbkF@shredder> (raw)
In-Reply-To: <20230608105648.266575-3-zahari.doychev@linux.com>
On Thu, Jun 08, 2023 at 12:56:47PM +0200, Zahari Doychev wrote:
> From: Zahari Doychev <zdoychev@maxlinear.com>
>
> Add support to the tc flower classifier to match based on fields in CFM
> information elements like level and opcode.
>
> tc filter add dev ens6 ingress protocol 802.1q \
> flower vlan_id 698 vlan_ethtype 0x8902 cfm mdl 5 op 46 \
> action drop
>
> Signed-off-by: Zahari Doychev <zdoychev@maxlinear.com>
> Reviewed-by: Simon Horman <simon.horman@corigine.com>
Reviewed-by: Ido Schimmel <idosch@nvidia.com>
next prev parent reply other threads:[~2023-06-08 12:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 10:56 [PATCH net-next v7 0/3] net: flower: add cfm support Zahari Doychev
2023-06-08 10:56 ` [PATCH net-next v7 1/3] net: flow_dissector: add support for cfm packets Zahari Doychev
2023-06-08 10:56 ` [PATCH net-next v7 2/3] net: flower: add support for matching cfm fields Zahari Doychev
2023-06-08 12:27 ` Ido Schimmel [this message]
2023-06-08 10:56 ` [PATCH net-next v7 3/3] selftests: net: add tc flower cfm test Zahari Doychev
2023-06-13 0:20 ` [PATCH net-next v7 0/3] net: flower: add cfm support patchwork-bot+netdevbpf
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=ZIHJLW71NjbuPbkF@shredder \
--to=idosch@idosch.org \
--cc=aleksander.lobakin@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hmehrtens@maxlinear.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=simon.horman@corigine.com \
--cc=xiyou.wangcong@gmail.com \
--cc=zahari.doychev@linux.com \
--cc=zdoychev@maxlinear.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.