From: Ferruh Yigit <ferruh.yigit@xilinx.com>
To: "Min Hu (Connor)" <humin29@huawei.com>,
Ke Zhang <ke1x.zhang@intel.com>, <chas3@att.com>, <dev@dpdk.org>
Subject: Re: [PATCH v3 1/1] net/bonding: fix rss key configuration when the key length is 52
Date: Wed, 4 May 2022 17:32:28 +0100 [thread overview]
Message-ID: <1a74f1d9-5798-b996-cbfd-23fc1e673876@xilinx.com> (raw)
In-Reply-To: <3f20d3e3-9a6e-7cfc-5181-5af5ff751d28@huawei.com>
On 4/13/2022 10:01 AM, Min Hu (Connor) wrote:
<...>
> 在 2022/4/11 13:40, Ke Zhang 写道:
>> when creating a bonding device, if the slave device's rss key length
>> = standard_rss_key length + extended_hash_key length, then bonding
>> device will be same as slave, in function bond_ethdev_configure(),
>> the default_rss_key length is 40, it is not matched, so it should
>> calculate a new key for bonding device if the default key could not
>> be used.
>>
>> Signed-off-by: Ke Zhang <ke1x.zhang@intel.com>
>
> Acked-by: Min Hu (Connor) <humin29@huawei.com>
>
Fixes: 6b1a001ec546 ("net/bonding: fix RSS key length")
Cc: stable@dpdk.org
(The fixes line not exactly true, since 52 byte keys seems not
considered from the begging, but above commit seems the closest one to
make the patch backported to proper releases.)
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2022-05-04 16:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 9:36 [PATCH] " Ke Zhang
2022-04-08 2:32 ` Min Hu (Connor)
2022-04-11 3:06 ` Zhang, Ke1X
2022-04-12 15:19 ` Stephen Hemminger
2022-04-13 9:03 ` Min Hu (Connor)
2022-04-13 16:12 ` Stephen Hemminger
2022-04-11 3:02 ` [PATCH v2 1/1] " Ke Zhang
2022-04-11 3:41 ` Min Hu (Connor)
2022-04-11 5:40 ` [PATCH v3 " Ke Zhang
2022-04-13 9:01 ` Min Hu (Connor)
2022-05-04 16:32 ` 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=1a74f1d9-5798-b996-cbfd-23fc1e673876@xilinx.com \
--to=ferruh.yigit@xilinx.com \
--cc=chas3@att.com \
--cc=dev@dpdk.org \
--cc=humin29@huawei.com \
--cc=ke1x.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).