From: "Chen, LingliX" <linglix.chen@intel.com>
To: "stable@dpdk.org" <stable@dpdk.org>,
"lihuisong@huawei.com" <lihuisong@huawei.com>
Cc: "Huang, ZhiminX" <zhiminx.huang@intel.com>,
"Jiale, SongX" <songx.jiale@intel.com>,
"Li, WeiyuanX" <weiyuanx.li@intel.com>,
"Jiang, YuX" <yux.jiang@intel.com>
Subject: RE: [PATCH 19.11] ethdev: fix RSS update when RSS is disabled
Date: Wed, 3 Aug 2022 03:05:17 +0000 [thread overview]
Message-ID: <SJ0PR11MB4893DFB3ADEC1C26116B5251909C9@SJ0PR11MB4893.namprd11.prod.outlook.com> (raw)
>
> -----Original Message-----
> From: Huisong Li <lihuisong@huawei.com>
> Sent: Tuesday, August 2, 2022 7:30 PM
> To: stable@dpdk.org; christian.ehrhardt@canonical.com
> Cc: liudongdong3@huawei.com; fengchengwen@huawei.com;
> huangdaode@huawei.com; Jiang, YuX <yux.jiang@intel.com>;
> lihuisong@huawei.com
> Subject: [PATCH 19.11] ethdev: fix RSS update when RSS is disabled
>
> [ upstream commit 93e1ea6dfa99dea359b8d66123576a395c2c0acd ]
>
> The ETH_MQ_RX_RSS_FLAG flag is a switch to enable RSS. If the flag is not set
> in dev_configure, RSS will be not configured and enabled.
> However, RSS hash and reta can still be configured by ethdev ops to enable RSS
> if the flag isn't set. The behavior is inconsistent.
>
> Bugzilla ID: 1056
> Fixes: 99a2dd955fba ("lib: remove librte_ prefix from directory names")
>
> Signed-off-by: Huisong Li <lihuisong@huawei.com>
> Signed-off-by: Min Hu (Connor) <humin29@huawei.com>
> Reviewed-by: Ferruh Yigit <ferruh.yigit@xilinx.com>
> ---
Tested-by: Lingli Chen <linglix.chen@intel.com>
next reply other threads:[~2022-08-03 3:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 3:05 Chen, LingliX [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-02 11:29 Huisong Li
2022-08-03 10:12 ` Christian Ehrhardt
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=SJ0PR11MB4893DFB3ADEC1C26116B5251909C9@SJ0PR11MB4893.namprd11.prod.outlook.com \
--to=linglix.chen@intel.com \
--cc=lihuisong@huawei.com \
--cc=songx.jiale@intel.com \
--cc=stable@dpdk.org \
--cc=weiyuanx.li@intel.com \
--cc=yux.jiang@intel.com \
--cc=zhiminx.huang@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).