From: Ferruh Yigit <ferruh.yigit@amd.com>
To: "Min Hu (Connor)" <humin29@huawei.com>
Cc: <stable@dpdk.org>, Chas Williams <chas3@att.com>,
Neil Horman <nhorman@tuxdriver.com>, <dev@dpdk.org>,
Thomas Monjalon <thomas@monjalon.net>,
David Marchand <david.marchand@redhat.com>
Subject: Re: [PATCH] net/bonding: fix mbuf fast free usage
Date: Tue, 24 May 2022 14:43:28 +0100 [thread overview]
Message-ID: <3581c8fc-0623-7c61-4c67-8b9ba40343f5@amd.com> (raw)
In-Reply-To: <20220521070814.35704-1-humin29@huawei.com>
On 5/21/2022 8:08 AM, Min Hu (Connor) wrote:
> [CAUTION: External Email]
>
> Usage of 'RTE_ETH_TX_OFFLOAD_MBUF_FAST_FREE' offload has two
> constraints: per-queue all mbufs comes from the same mempool and
> has refcnt = 1.
>
> Bonding mode Broadcast, Tx mbuf has more than one refcnt.
> Bonding mode 8023AD, It contains two mempools separately for LACP
> packets and other packets. In Tx or Rx, Fast mbuf free will operate
> mbuf from different mempool.
>
> This patch will prevent 'RTE_ETH_TX_OFFLOAD_MBUF_FAST_FREE' offload
> when in bonding mode Broadcast and mode 8023AD.
>
Hi Connor,
Please find a few syntax comment below, rest lgtm.
> Fixes: 78aecefed955 ("bond: move param parsing in configure step")
> Cc: stable@dpdk.org
>
> Signed-off-by: Min Hu (Connor) <humin29@huawei.com>
> ---
> drivers/net/bonding/rte_eth_bond_pmd.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/drivers/net/bonding/rte_eth_bond_pmd.c b/drivers/net/bonding/rte_eth_bond_pmd.c
> index c929b55768..5ca90c7590 100644
> --- a/drivers/net/bonding/rte_eth_bond_pmd.c
> +++ b/drivers/net/bonding/rte_eth_bond_pmd.c
> @@ -3563,6 +3563,7 @@ bond_ethdev_configure(struct rte_eth_dev *dev)
> const char *name = dev->device->name;
> struct bond_dev_private *internals = dev->data->dev_private;
> struct rte_kvargs *kvlist = internals->kvlist;
> + uint64_t offloads;
> int arg_count;
> uint16_t port_id = dev - rte_eth_devices;
> uint8_t agg_mode;
> @@ -3613,6 +3614,15 @@ bond_ethdev_configure(struct rte_eth_dev *dev)
> }
> }
>
> + offloads = dev->data->dev_conf.txmode.offloads;
> + if ((offloads & RTE_ETH_TX_OFFLOAD_MBUF_FAST_FREE) &&
> + (internals->mode == BONDING_MODE_8023AD ||
> + internals->mode == BONDING_MODE_BROADCAST)) {
Can you indent above two lines one more tab, to differentiate them from
content of the if block.
> + RTE_BOND_LOG(WARNING, "BOND MODE Broadcast & 8023AD don't support MBUF_FAST_FREE offload, force disable it.");
- Why "BOND MODE" is uppercase, if there is no special reason for it, I
suggest using lower case.
- Can you break the message to next line, this enables shorter line
without breaking the message:
RTE_BOND_LOG(WARNING,
"BOND MODE Broadcast & 8023AD don't support ....
> + offloads &= ~RTE_ETH_TX_OFFLOAD_MBUF_FAST_FREE;
> + dev->data->dev_conf.txmode.offloads = offloads;
> + }
> +
> /* set the max_rx_pktlen */
> internals->max_rx_pktlen = internals->candidate_max_rx_pktlen;
>
> --
> 2.33.0
>
next prev parent reply other threads:[~2022-05-24 13:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-21 7:08 Min Hu (Connor)
2022-05-24 13:43 ` Ferruh Yigit [this message]
2022-05-25 1:11 ` Min Hu (Connor)
2022-05-25 1:08 ` [PATCH v2] " Min Hu (Connor)
2022-05-25 17:44 ` Ferruh Yigit
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=3581c8fc-0623-7c61-4c67-8b9ba40343f5@amd.com \
--to=ferruh.yigit@amd.com \
--cc=chas3@att.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=humin29@huawei.com \
--cc=nhorman@tuxdriver.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).