From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Wenjun Wu <wenjun1.wu@intel.com>,
dev@dpdk.org, jingjing.wu@intel.com, beilei.xing@intel.com
Cc: stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH v4] net/iavf: fix wrong RSS hash update
Date: Wed, 24 Mar 2021 14:47:05 +0000 [thread overview]
Message-ID: <55d011a6-656c-1398-68c1-2a8bdc66c4a3@intel.com> (raw)
In-Reply-To: <20210315005953.32112-1-wenjun1.wu@intel.com>
On 3/15/2021 12:59 AM, Wenjun Wu wrote:
> This patch change judgment statements to disable RSS for vf
> when users need to disable RSS or RSS hash function configured
> is not supported.
>
> Fixes: 95f2f0e9fc2a ("net/iavf: improve default RSS")
> Cc: stable@dpdk.org
>
> Signed-off-by: Wenjun Wu <wenjun1.wu@intel.com>
>
> ---
> v4: clear existing RSS when rss_hf = 0.
> v3: fix the same issue for both pf and vf.
Applied to dpdk-next-net-intel.
prev parent reply other threads:[~2021-03-24 14:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210305060424.21917-1>
2021-03-15 0:59 ` Wenjun Wu
2021-03-24 14:47 ` Ferruh Yigit [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=55d011a6-656c-1398-68c1-2a8bdc66c4a3@intel.com \
--to=ferruh.yigit@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=stable@dpdk.org \
--cc=wenjun1.wu@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).