From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: Lance Richardson <lance.richardson@broadcom.com>
Cc: dpdk-dev <dev@dpdk.org>, Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH] net/bnxt: fix mbuf free when clearing Tx queue
Date: Wed, 23 Oct 2019 11:40:22 -0400 [thread overview]
Message-ID: <CACZ4nhsf4znj+NKubTeRPigKb6SqUi9SS2jgY6w3C3vGwSWjCw@mail.gmail.com> (raw)
In-Reply-To: <20191023142735.17571-1-lance.richardson@broadcom.com>
On Wed, Oct 23, 2019 at 10:27 AM Lance Richardson <
lance.richardson@broadcom.com> wrote:
> When freeing pending transmit mbufs, use rte_pktmbuf_free_seg()
> instead of rte_pktmbuf_free(), otherwise linked mbufs may be freed
> more than once.
>
> Fixes: 6eb3cc2294fd ("net/bnxt: add initial Tx code")
> Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
> Signed-off-by: Lance Richardson <lance.richardson@broadcom.com>
>
Patch applied to dpdk-next-net-brcm
prev parent reply other threads:[~2019-10-23 15:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 14:27 Lance Richardson
2019-10-23 15:40 ` Ajit Khaparde [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=CACZ4nhsf4znj+NKubTeRPigKb6SqUi9SS2jgY6w3C3vGwSWjCw@mail.gmail.com \
--to=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=lance.richardson@broadcom.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).