From: Kevin Traynor <ktraynor@redhat.com>
To: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH 18.11] net/cxgbe: fix queue DMA ring leaks during port close
Date: Thu, 3 Dec 2020 16:42:41 +0000 [thread overview]
Message-ID: <d273a194-9a5b-7a99-bf9d-1562d3d6cb3c@redhat.com> (raw)
In-Reply-To: <1606927521-27331-1-git-send-email-rahul.lakkireddy@chelsio.com>
On 02/12/2020 16:45, Rahul Lakkireddy wrote:
> [ upstream commit 6b78a629954c3857d4bc651a673fe102958a12db ]
>
> Free up the DMA memzones properly for all the port's queues during
> port close. So, rework DMA ring allocation/free logic to use
> rte_eth_dma_zone_reserve()/rte_eth_dma_zone_free() helper functions
> for allocating/freeing the memzones.
>
> The firmware event queue doesn't have an associated freelist queue.
> So, remove check that tries to give memzone name for a non-existent
> freelist queue.
>
> Also, add a missing free for the control queue mempools.
>
> Fixes: 0462d115441d ("cxgbe: add device related operations")
>
> Signed-off-by: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
Applied, thanks.
prev parent reply other threads:[~2020-12-03 16:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 16:45 Rahul Lakkireddy
2020-12-03 16:42 ` Kevin Traynor [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=d273a194-9a5b-7a99-bf9d-1562d3d6cb3c@redhat.com \
--to=ktraynor@redhat.com \
--cc=rahul.lakkireddy@chelsio.com \
--cc=stable@dpdk.org \
/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).