From: "Yang, Qiming" <qiming.yang@intel.com>
To: "Zhang, Qi Z" <qi.z.zhang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/ice/base: fix wrong symmetric hash configure
Date: Mon, 4 Nov 2019 03:16:30 +0000 [thread overview]
Message-ID: <F5DF4F0E3AFEF648ADC1C3C33AD4DBF17A57143B@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20191031035521.45015-1-qi.z.zhang@intel.com>
Hi,
Some typos.
> -----Original Message-----
> From: Zhang, Qi Z
> Sent: Thursday, October 31, 2019 11:55 AM
> To: Yang, Qiming <qiming.yang@intel.com>
> Cc: dev@dpdk.org; Zhang, Qi Z <qi.z.zhang@intel.com>
> Subject: [PATCH] net/ice/base: fix wrong symmetric hash configure
>
> When a new hash profie is created, we need to reset all related
profie / profile
> GLQF_HSYMM registers, otherwise unexpected hash behaviour may happens
behaviour / behavior
> on packet that hit that profile.
>
> The patch fix the issue that we only do reset when symmetric hash is
Fix/fixes
> required, but actually for non symmmetric hash we also need this, since
symmmetric / symmetric
> GLQF_HSYMM might be polluted by previous configuration.
>
> Fixes: ddae0440353f ("net/ice/base: enable symmetric hash for RSS")
>
> Signed-off-by: Qi Zhang <qi.z.zhang@intel.com>
> Tested-by: Simei Su <simei.su@intel.com>
> ---
> drivers/net/ice/base/ice_flow.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/drivers/net/ice/base/ice_flow.c b/drivers/net/ice/base/ice_flow.c
> index d2dbb1177..797d7e6e6 100644
> --- a/drivers/net/ice/base/ice_flow.c
> +++ b/drivers/net/ice/base/ice_flow.c
> @@ -2199,8 +2199,6 @@ ice_add_rss_cfg_sync(struct ice_hw *hw, u16
> vsi_handle, u64 hashed_flds,
> status = ice_add_rss_list(hw, vsi_handle, prof);
>
> prof->cfg.symm = symm;
> - if (!symm)
> - goto exit;
>
> update_symm:
> ice_rss_update_symm(hw, prof);
> --
> 2.13.6
next prev parent reply other threads:[~2019-11-04 3:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 3:55 Qi Zhang
2019-11-04 3:16 ` Yang, Qiming [this message]
2019-11-04 3:19 ` Ye Xiaolong
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=F5DF4F0E3AFEF648ADC1C3C33AD4DBF17A57143B@SHSMSX101.ccr.corp.intel.com \
--to=qiming.yang@intel.com \
--cc=dev@dpdk.org \
--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).