From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Guo, Junfeng" <junfeng.guo@intel.com>,
"Wu, Jingjing" <jingjing.wu@intel.com>,
"Xing, Beilei" <beilei.xing@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] net/ice: refactor RSS config for potential bugs
Date: Tue, 13 Oct 2020 07:51:50 +0000 [thread overview]
Message-ID: <6763c1102f2c41ffafe85fddcf33697f@intel.com> (raw)
In-Reply-To: <20201013062555.1120324-1-junfeng.guo@intel.com>
> -----Original Message-----
> From: Guo, Junfeng <junfeng.guo@intel.com>
> Sent: Tuesday, October 13, 2020 2:26 PM
> To: Zhang, Qi Z <qi.z.zhang@intel.com>; Wu, Jingjing <jingjing.wu@intel.com>;
> Xing, Beilei <beilei.xing@intel.com>
> Cc: dev@dpdk.org; Guo, Junfeng <junfeng.guo@intel.com>
> Subject: [PATCH v2] net/ice: refactor RSS config for potential bugs
Renamed to refactor RSS config wrap and fix potential bugs
>
> Current implementation for PF RSS config wrap function has some potential
> bugs about GTPU, e.g., same input set for GTPU inner and non-TUN have
> different hash values, which should be same. Thus, we use extra pre and post
> processing to re-config GTPU rules.
>
> Signed-off-by: Junfeng Guo <junfeng.guo@intel.com>
Acked-by: Qi Zhang <qi.z.zhang@intel.com>
Applied to dpdk-next-net-intel with fixline be added
Added fix line: Fixes: 185fe122f489 ("net/ice: fix GTPU down/uplink and extension conflict")
Thanks
Qi
prev parent reply other threads:[~2020-10-13 7:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 7:54 [dpdk-dev] [PATCH] " Junfeng Guo
2020-10-13 6:25 ` [dpdk-dev] [PATCH v2] " Junfeng Guo
2020-10-13 7:51 ` 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=6763c1102f2c41ffafe85fddcf33697f@intel.com \
--to=qi.z.zhang@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=junfeng.guo@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).