From: "Wu, Wenjun1" <wenjun1.wu@intel.com>
To: "Yigit, Ferruh" <ferruh.yigit@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Wu, Jingjing" <jingjing.wu@intel.com>,
"Xing, Beilei" <beilei.xing@intel.com>,
"Zhang, Qi Z" <qi.z.zhang@intel.com>
Subject: Re: [dpdk-dev] [PATCH] net/iavf: support FDIR L3 fields for IP fragment packets
Date: Tue, 17 Aug 2021 06:35:02 +0000 [thread overview]
Message-ID: <SA0PR11MB4575248A90A2F229AF96F5B6DFFE9@SA0PR11MB4575.namprd11.prod.outlook.com> (raw)
In-Reply-To: <5b2dd6ae-b3fd-7d7b-5e80-90f838b633fb@intel.com>
Hi Ferruh,
I am sorry my description caused confusion. I will split this patch into two, rework the commit log and send it later.
> -----Original Message-----
> From: Yigit, Ferruh <ferruh.yigit@intel.com>
> Sent: Friday, August 13, 2021 10:00 PM
> To: Wu, Wenjun1 <wenjun1.wu@intel.com>; dev@dpdk.org; Wu, Jingjing
> <jingjing.wu@intel.com>; Xing, Beilei <beilei.xing@intel.com>; Zhang, Qi Z
> <qi.z.zhang@intel.com>
> Subject: Re: [dpdk-dev] [PATCH] net/iavf: support FDIR L3 fields for IP
> fragment packets
>
> On 8/2/2021 8:57 AM, Wenjun Wu wrote:
> > Add support of FDIR L3 fields for both IPv4 and IPv6 fragment packets.
> >
>
> Description mentions from both IPv4 & IPv6 but only IPv6 macro is updated,
> is this expected?
>
> Is following correct:
> Before this patch flow director rules were not applied to fragmented IPv4 &
> IPv6 packets (so packets were not able to sent to specific queues), but after
> this patch it does.
> Is it the case that HW configuration was missing and hash is not calculated for
> these kind of packets etc.. If you have more details can you please provide?
> Also what was happening to these packets previously, sent to queue 0 by
> default?
>
> Overall can please provide more description and check below question
> related to 'field_selector'?
>
> Thanks,
> ferruh
>
> > Signed-off-by: Wenjun Wu <wenjun1.wu@intel.com>
> > ---
> > drivers/net/iavf/iavf_fdir.c | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/net/iavf/iavf_fdir.c
> > b/drivers/net/iavf/iavf_fdir.c index da3eec8b59..32b06044f2 100644
> > --- a/drivers/net/iavf/iavf_fdir.c
> > +++ b/drivers/net/iavf/iavf_fdir.c
> > @@ -57,7 +57,7 @@
> > IAVF_INSET_IPV6_HOP_LIMIT)
> >
> > #define IAVF_FDIR_INSET_ETH_IPV6_FRAG_EXT (\
> > - IAVF_INSET_IPV6_ID)
> > + IAVF_FDIR_INSET_ETH_IPV6 | IAVF_INSET_IPV6_ID)
> >
> > #define IAVF_FDIR_INSET_ETH_IPV6_UDP (\
> > IAVF_INSET_IPV6_SRC | IAVF_INSET_IPV6_DST | \ @@ -664,6 +664,7
> @@
> > iavf_fdir_add_fragment_hdr(struct virtchnl_proto_hdrs *hdrs, int layer)
> > /* adding dummy fragment header */
> > hdr1 = &hdrs->proto_hdr[layer];
> > VIRTCHNL_SET_PROTO_HDR_TYPE(hdr1, IPV4_FRAG);
> > + hdr1->field_selector = 0;
>
> Is this change related to new support, or fixing something that was missing
> previously?
>
> > hdrs->count = ++layer;
> > }
> >
> >
next prev parent reply other threads:[~2021-08-17 6:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 7:57 Wenjun Wu
2021-08-10 7:42 ` Zhang, Qi Z
2021-08-13 13:59 ` Ferruh Yigit
2021-08-17 6:35 ` Wu, Wenjun1 [this message]
2021-08-17 6:49 ` [dpdk-dev] [PATCH v2] net/iavf: fix wrong FDIR L3 field set for IPv4 " Wenjun Wu
2021-08-29 11:18 ` Zhang, Qi Z
2021-08-17 6:50 ` [dpdk-dev] [PATCH v2] net/iavf: support FDIR L3 fields for IPv6 " Wenjun Wu
2021-08-29 11:21 ` 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=SA0PR11MB4575248A90A2F229AF96F5B6DFFE9@SA0PR11MB4575.namprd11.prod.outlook.com \
--to=wenjun1.wu@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jingjing.wu@intel.com \
--cc=qi.z.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).