From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Yuying Zhang <yuying.zhang@intel.com>, <dev@dpdk.org>,
<qi.z.zhang@intel.com>
Subject: Re: [PATCH v3 2/2] net/ice: support drop any and steer all to queue
Date: Thu, 10 Feb 2022 16:59:42 +0000 [thread overview]
Message-ID: <2629ea74-0ae7-4d23-2e29-0eda3c65fa3c@intel.com> (raw)
In-Reply-To: <20220126155710.911525-2-yuying.zhang@intel.com>
On 1/26/2022 3:57 PM, Yuying Zhang wrote:
> This patch supports drop any and steer all to queue in switch
> filter. Support new rte_flow pattern any to handle all packets.
> The usage is listed below.
>
> 1. drop any:
> flow create 0 ingress pattern any / end actions drop / end
> All packets received in port 0 will be dropped.
>
> 2. steer all to queue:
> flow create 0 ingress pattern any / end actions queue index 3 / end
> All packets received in port 0 will be steered to queue 3.
>
> Signed-off-by: Yuying Zhang<yuying.zhang@intel.com>
> ---
> drivers/net/ice/ice_generic_flow.c | 6 ++++++
> drivers/net/ice/ice_generic_flow.h | 3 +++
> drivers/net/ice/ice_switch_filter.c | 6 ++++++
> 3 files changed, 15 insertions(+)
Documentation is missing, 'check-doc-vs-code.sh' gives following error.
$ ./devtools/check-doc-vs-code.sh
rte_flow doc out of sync for ice
item any
I will fix it in next-net while merging
next prev parent reply other threads:[~2022-02-10 17:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <http://patchwork.dpdk.org/project/dpdk/patch/20220118145750.718362-1-yuying.zhang@intel.com/>
2022-01-26 15:57 ` [PATCH v3 1/2] net/ice/base: add profile validation on switch filter Yuying Zhang
2022-01-26 15:57 ` [PATCH v3 2/2] net/ice: support drop any and steer all to queue Yuying Zhang
2022-02-09 2:18 ` Zhang, Qi Z
2022-02-10 16:59 ` Ferruh Yigit [this message]
2022-02-09 2:15 ` [PATCH v3 1/2] net/ice/base: add profile validation on switch filter Zhang, Qi Z
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=2629ea74-0ae7-4d23-2e29-0eda3c65fa3c@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=qi.z.zhang@intel.com \
--cc=yuying.zhang@intel.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).