From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Zhang, Yuying" <yuying.zhang@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Wu, Jingjing" <jingjing.wu@intel.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] net/iavf: support FDIR TCP/UDP pattern without input set
Date: Thu, 7 Jan 2021 04:37:33 +0000 [thread overview]
Message-ID: <0381a371ac5344f1b68023ca60416953@intel.com> (raw)
In-Reply-To: <20210106104913.48459-1-yuying.zhang@intel.com>
> -----Original Message-----
> From: Zhang, Yuying <yuying.zhang@intel.com>
> Sent: Wednesday, January 6, 2021 6:49 PM
> To: dev@dpdk.org; Zhang, Qi Z <qi.z.zhang@intel.com>; Wu, Jingjing
> <jingjing.wu@intel.com>; Yigit, Ferruh <ferruh.yigit@intel.com>
> Cc: Zhang, Yuying <yuying.zhang@intel.com>
> Subject: [PATCH v2] net/iavf: support FDIR TCP/UDP pattern without input set
>
> This patch adds an input set refinement function to support outer and inner
> TCP/UDP patterns without input set for flow director filter.
>
> 1. flow create 0 ingress pattern eth / ipv4 / udp / end
> actions rss queues 0 1 2 3 end / end
> 2. flow create 0 ingress pattern eth / ipv6 / tcp / end
> actions queue index 3 / end
> This patch supports above patterns which can't be created currently.
Refine the commit a little bit as below:
This patch will refine the inputset when it is empty and generate
a dummy proto type as inputset in l3 header which is required
by the hardware.
>
> Signed-off-by: Yuying Zhang <yuying.zhang@intel.com>
Acked-by: Qi Zhang <qi.z.zhang@intel.com>
Applied to dpdk-next-net-intel after reverted v1.
Thanks
Qi
prev parent reply other threads:[~2021-01-07 4:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-01 8:32 [dpdk-dev] [PATCH v1] " Yuying Zhang
2020-12-23 8:12 ` Zhang, Qi Z
2021-01-04 15:21 ` Ferruh Yigit
2021-01-06 10:49 ` [dpdk-dev] [PATCH v2] " Yuying Zhang
2021-01-07 4:37 ` Zhang, Qi Z [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=0381a371ac5344f1b68023ca60416953@intel.com \
--to=qi.z.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jingjing.wu@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).