All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@xilinx.com>
To: "Min Hu (Connor)" <humin29@huawei.com>, <dev@dpdk.org>
Cc: <stable@dpdk.org>, Chas Williams <chas3@att.com>,
	Thomas Monjalon <thomas.monjalon@6wind.com>,
	David Marchand <david.marchand@6wind.com>,
	Neil Horman <nhorman@tuxdriver.com>
Subject: Re: [PATCH v2] net/bonding: fix mbuf fast free usage
Date: Wed, 25 May 2022 18:44:32 +0100	[thread overview]
Message-ID: <77d365ca-4468-3683-ab57-75df1dc3415d@xilinx.com> (raw)
In-Reply-To: <20220525010828.39276-1-humin29@huawei.com>

On 5/25/2022 2:08 AM, Min Hu (Connor) wrote:
> 
> 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.
> 
> Fixes: 78aecefed955 ("bond: move param parsing in configure step")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Min Hu (Connor) <humin29@huawei.com>

Applied to dpdk-next-net/main, thanks.


      reply	other threads:[~2022-05-25 17:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-21  7:08 [PATCH] net/bonding: fix mbuf fast free usage Min Hu (Connor)
2022-05-24 13:43 ` Ferruh Yigit
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 [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=77d365ca-4468-3683-ab57-75df1dc3415d@xilinx.com \
    --to=ferruh.yigit@xilinx.com \
    --cc=chas3@att.com \
    --cc=david.marchand@6wind.com \
    --cc=dev@dpdk.org \
    --cc=humin29@huawei.com \
    --cc=nhorman@tuxdriver.com \
    --cc=stable@dpdk.org \
    --cc=thomas.monjalon@6wind.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.