DPDK patches and discussions
 help / color / mirror / Atom feed
From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
To: "humin (Q)" <humin29@huawei.com>,
	Huisong Li <lihuisong@huawei.com>,
	dev@dpdk.org
Cc: ferruh.yigit@amd.com, 3chas3@gmail.com, liudongdong3@huawei.com,
	huangdaode@huawei.com
Subject: Re: [PATCH V3] app/testpmd: update bond port configurations when add slave
Date: Sun, 6 Nov 2022 13:04:40 +0300	[thread overview]
Message-ID: <c6d56214-34fb-7f60-9c40-d0de9fa9ac49@oktetlabs.ru> (raw)
In-Reply-To: <9c1c20bf-9c41-5a82-7613-6124f8c496c4@huawei.com>

On 11/1/22 06:41, humin (Q) wrote:
> Reviewed-by: Min Hu (Connor) <humin29huawei.com>
> 
> 在 2022/10/29 11:50, Huisong Li 写道:
>> Some capabilities (like, rx_offload_capa and tx_offload_capa) of bonding
>> device in dev_info is zero when no slave is added. And its capability 
>> will
>> be updated when add a new slave device.
>>
>> The capability to update dynamically may introduce some problems if not
>> handled properly. For example, the reconfig() is called to initialize
>> bonding port configurations when create a bonding device. The global
>> tx_mode is assigned to dev_conf.txmode. The DEV_TX_OFFLOAD_MBUF_FAST_FREE
>> which is the default value of global tx_mode.offloads in testpmd is 
>> removed
>> from bonding device configuration because of zero rx_offload_capa.
>> As a result, this offload isn't set to bonding device.
>>
>> Generally, port configurations of bonding device must be within the
>> intersection of the capability of all slave devices. If use original port
>> configurations, the removed capabilities because of adding a new slave 
>> may
>> cause failure when re-initialize bonding device.
>>
>> So port configurations of bonding device also need to be updated 
>> because of
>> the added and removed capabilities. In addition, this also helps to 
>> ensure
>> consistency between testpmd and bonding device.
>>
>> Signed-off-by: Huisong Li <lihuisong@huawei.com>
>> ---
>>   - v3: fix code comment
>>   - v2: fix a spelling error in commit log

It fails to apply on dpdk-next-net/main. Could you rebase it,
please, and send v4. Thanks.



  reply	other threads:[~2022-11-06 10:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-28  3:53 [PATCH] " Huisong Li
2022-10-28  6:20 ` [PATCH V2] " Huisong Li
2022-10-28 10:59   ` humin (Q)
2022-10-29  3:29     ` lihuisong (C)
2022-10-29  3:50 ` [PATCH V3] " Huisong Li
2022-11-01  3:41   ` humin (Q)
2022-11-06 10:04     ` Andrew Rybchenko [this message]
2022-11-07  2:03 ` [PATCH V4] " Huisong Li
2022-11-07  2:18 ` [PATCH V5] " Huisong Li
2022-11-07  5:36   ` 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=c6d56214-34fb-7f60-9c40-d0de9fa9ac49@oktetlabs.ru \
    --to=andrew.rybchenko@oktetlabs.ru \
    --cc=3chas3@gmail.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.com \
    --cc=huangdaode@huawei.com \
    --cc=humin29@huawei.com \
    --cc=lihuisong@huawei.com \
    --cc=liudongdong3@huawei.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).