DPDK patches and discussions
 help / color / mirror / Atom feed
From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
To: Dongdong Liu <liudongdong3@huawei.com>, dev@dpdk.org
Cc: yux.jiang@intel.com, zhiminx.huang@intel.com,
	qingx.sun@intel.com, ferruh.yigit@xilinx.com,
	songx.jiale@intel.com, stable@dpdk.org,
	Huisong Li <lihuisong@huawei.com>, Chas Williams <chas3@att.com>,
	"Min Hu (Connor)" <humin29@huawei.com>,
	Declan Doherty <declan.doherty@intel.com>,
	Tomasz Kulasek <tomaszx.kulasek@intel.com>
Subject: Re: [PATCH 1/2] net/bonding: fix RSS inconsistent between bonded and slaves
Date: Thu, 9 Jun 2022 11:52:38 +0300	[thread overview]
Message-ID: <c042f4bc-00de-c48b-a85f-26aa02f7805a@oktetlabs.ru> (raw)
In-Reply-To: <20220608114548.25837-2-liudongdong3@huawei.com>

On 6/8/22 14:45, Dongdong Liu wrote:
> From: Huisong Li <lihuisong@huawei.com>
> 
> Currently, RSS configuration of slave is set only when RSS is enabled for
> bonded port. If RSS is enabled for the slaves port before adding to the
> bonded port with disabling RSS, it will run into that the RSS enabled state
> of bonded and slaves port is inconsistent after starting bonded port.
> So the RSS configuration of slave should also be set when RSS is disabled
> for bonded port.
> 
> Fixes: 734ce47f71e0 ("bonding: support RSS dynamic configuration")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Huisong Li <lihuisong@huawei.com>
> Signed-off-by: Dongdong Liu <liudongdong3@huawei.com>

Reviewed-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>


  reply	other threads:[~2022-06-09  8:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-08 11:45 [PATCH 0/2] app/test: fix bonding RSS test when disable RSS Dongdong Liu
2022-06-08 11:45 ` [PATCH 1/2] net/bonding: fix RSS inconsistent between bonded and slaves Dongdong Liu
2022-06-09  8:52   ` Andrew Rybchenko [this message]
2022-06-08 11:45 ` [PATCH 2/2] app/test: fix bonding RSS test when disable RSS Dongdong Liu
2022-06-09  8:53 ` [PATCH 0/2] " Andrew Rybchenko

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=c042f4bc-00de-c48b-a85f-26aa02f7805a@oktetlabs.ru \
    --to=andrew.rybchenko@oktetlabs.ru \
    --cc=chas3@att.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@xilinx.com \
    --cc=humin29@huawei.com \
    --cc=lihuisong@huawei.com \
    --cc=liudongdong3@huawei.com \
    --cc=qingx.sun@intel.com \
    --cc=songx.jiale@intel.com \
    --cc=stable@dpdk.org \
    --cc=tomaszx.kulasek@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).