DPDK patches and discussions
 help / color / mirror / Atom feed
From: "humin (Q)" <humin29@huawei.com>
To: Huisong Li <lihuisong@huawei.com>, <dev@dpdk.org>
Cc: <ferruh.yigit@amd.com>, <andrew.rybchenko@oktetlabs.ru>,
	<liudongdong3@huawei.com>, <huangdaode@huawei.com>
Subject: Re: [PATCH] net/bonding: fix slave device Rx/Tx offload configuration
Date: Tue, 1 Nov 2022 10:34:17 +0800	[thread overview]
Message-ID: <ff1b3a5a-bafb-2229-bcbc-50060d84fd19@huawei.com> (raw)
In-Reply-To: <20221028023646.32585-1-lihuisong@huawei.com>

Acked-by: Min Hu (Connor) <humin29@huawei.com>

在 2022/10/28 10:36, Huisong Li 写道:
> Normally, the Rx/Tx offload capability of bonding interface is
> the intersection of the capability of all slave devices. And
> Rx/Tx offloads configuration of slave device comes from bonding
> interface. But now there is a risk that slave device retains its
> previous offload configurations which is not within the offload
> configurations of bond interface.
>
> Fixes: 57b156540f51 ("net/bonding: fix offloading configuration")
> Cc: stable@dpdk.org
>
> Signed-off-by: Huisong Li <lihuisong@huawei.com>
> ---
>   drivers/net/bonding/rte_eth_bond_pmd.c | 17 ++++-------------
>   1 file changed, 4 insertions(+), 13 deletions(-)
>
> diff --git a/drivers/net/bonding/rte_eth_bond_pmd.c b/drivers/net/bonding/rte_eth_bond_pmd.c
> index dc74852137..ca87490065 100644
> --- a/drivers/net/bonding/rte_eth_bond_pmd.c
> +++ b/drivers/net/bonding/rte_eth_bond_pmd.c
> @@ -1741,20 +1741,11 @@ slave_configure(struct rte_eth_dev *bonded_eth_dev,
>   	slave_eth_dev->data->dev_conf.link_speeds =
>   			bonded_eth_dev->data->dev_conf.link_speeds;
>   
> -	slave_eth_dev->data->dev_conf.txmode.offloads |=
> -		bonded_eth_dev->data->dev_conf.txmode.offloads;
> -
> -	slave_eth_dev->data->dev_conf.txmode.offloads &=
> -		(bonded_eth_dev->data->dev_conf.txmode.offloads |
> -		~internals->tx_offload_capa);
> -
> -	slave_eth_dev->data->dev_conf.rxmode.offloads |=
> -		bonded_eth_dev->data->dev_conf.rxmode.offloads;
> -
> -	slave_eth_dev->data->dev_conf.rxmode.offloads &=
> -		(bonded_eth_dev->data->dev_conf.rxmode.offloads |
> -		~internals->rx_offload_capa);
> +	slave_eth_dev->data->dev_conf.txmode.offloads =
> +			bonded_eth_dev->data->dev_conf.txmode.offloads;
>   
> +	slave_eth_dev->data->dev_conf.rxmode.offloads =
> +			bonded_eth_dev->data->dev_conf.rxmode.offloads;
>   
>   	nb_rx_queues = bonded_eth_dev->data->nb_rx_queues;
>   	nb_tx_queues = bonded_eth_dev->data->nb_tx_queues;

  reply	other threads:[~2022-11-01  2:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-28  2:36 Huisong Li
2022-11-01  2:34 ` humin (Q) [this message]
2022-11-06  9:45   ` 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=ff1b3a5a-bafb-2229-bcbc-50060d84fd19@huawei.com \
    --to=humin29@huawei.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.com \
    --cc=huangdaode@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).