From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>, dev@dpdk.org
Cc: kaara.satwik@chelsio.com
Subject: Re: [dpdk-dev] [PATCH 0/2] net/cxgbe: release port resources during port close
Date: Fri, 18 Sep 2020 15:57:18 +0100 [thread overview]
Message-ID: <19102234-dcd4-a35c-f6dd-2b128ac3a4ec@intel.com> (raw)
In-Reply-To: <cover.1598979347.git.rahul.lakkireddy@chelsio.com>
On 9/1/2020 6:16 PM, Rahul Lakkireddy wrote:
> Patch 1 fixes queue DMA ring leaks seen during port close.
>
> Patch 2 enables RTE_ETH_DEV_CLOSE_REMOVE and reworks resources
> release logic for port close.
>
> Thanks,
> Rahul
>
>
> Rahul Lakkireddy (2):
> net/cxgbe: fix queue DMA ring leaks during port close
> net/cxgbe: release port resources during port close
>
Series applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2020-09-18 14:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-01 17:16 Rahul Lakkireddy
2020-09-01 17:16 ` [dpdk-dev] [PATCH 1/2] net/cxgbe: fix queue DMA ring leaks " Rahul Lakkireddy
2020-09-01 17:16 ` [dpdk-dev] [PATCH 2/2] net/cxgbe: release port resources " Rahul Lakkireddy
2020-09-17 12:46 ` Ferruh Yigit
2020-09-18 13:18 ` Rahul Lakkireddy
2020-09-18 14:38 ` Ferruh Yigit
2020-09-18 14:57 ` 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=19102234-dcd4-a35c-f6dd-2b128ac3a4ec@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=kaara.satwik@chelsio.com \
--cc=rahul.lakkireddy@chelsio.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).