From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Su, Simei" <simei.su@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Zhao1, Wei" <wei.zhao1@intel.com>,
"Jiang, JunyuX" <junyux.jiang@intel.com>,
"Lu, Nannan" <nannan.lu@intel.com>
Subject: Re: [dpdk-dev] [PATCH] net/ice: fix GTPU/PPPoE packets with no hash value
Date: Tue, 7 Jul 2020 02:29:59 +0000 [thread overview]
Message-ID: <039ED4275CED7440929022BC67E706115485514A@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1594085898-138749-1-git-send-email-simei.su@intel.com>
> -----Original Message-----
> From: Su, Simei <simei.su@intel.com>
> Sent: Tuesday, July 7, 2020 9:38 AM
> To: Zhang, Qi Z <qi.z.zhang@intel.com>
> Cc: dev@dpdk.org; Zhao1, Wei <wei.zhao1@intel.com>; Jiang, JunyuX
> <junyux.jiang@intel.com>; Lu, Nannan <nannan.lu@intel.com>; Su, Simei
> <simei.su@intel.com>
> Subject: [PATCH] net/ice: fix GTPU/PPPoE packets with no hash value
>
> When RSS init, because of profile overlap, the GTPU_IPV4 packets don't hit
> GTPU_INNER_IPV4 profile which causes no hash value. Because of no PPPoE
> profile, the PPPoE packets also has no hash value. This patch solves this issue
> by pulling GTPU_IPV4 profile into inner ipv4 group and creating related
> PPPoE profile at the same time.
>
> Fixes: 8cadc41294c6 ("net/ice: initialize and update RSS based on user
> config")
>
> Signed-off-by: Simei Su <simei.su@intel.com>
Acked-by: Qi Zhang <qi.z.zhang@intel.com>
Applied to dpdk-next-net-intel.
Thanks
Qi
next prev parent reply other threads:[~2020-07-07 2:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 1:38 Simei Su
2020-07-07 2:29 ` Zhang, Qi Z [this message]
2020-07-07 3:09 ` 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=039ED4275CED7440929022BC67E706115485514A@SHSMSX103.ccr.corp.intel.com \
--to=qi.z.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=junyux.jiang@intel.com \
--cc=nannan.lu@intel.com \
--cc=simei.su@intel.com \
--cc=wei.zhao1@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).