From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Peters, Matt" <Matt.Peters@windriver.com>,
"Legacy, Allain" <Allain.Legacy@windriver.com>,
"thomas@monjalon.net" <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v3] net/avp: remove resources when port is closed
Date: Tue, 25 Jun 2019 18:27:38 +0100 [thread overview]
Message-ID: <9c67c4e4-fa4f-6623-c0c8-157765e04ae1@intel.com> (raw)
In-Reply-To: <CDC594423E6E584382202A0DD5728E57C1362684@ALA-MBD.corp.ad.wrs.com>
On 6/19/2019 12:33 PM, Peters, Matt wrote:
>> -----Original Message-----
>> From: Legacy, Allain
>> Sent: Tuesday, June 18, 2019 3:19 PM
>> To: thomas@monjalon.net
>> Cc: dev@dpdk.org; ferruh.yigit@intel.com; Peters, Matt
>> Subject: [PATCH v3] net/avp: remove resources when port is closed
>>
>> The rte_eth_dev_close() function now handles freeing resources for
>> devices (e.g., mac_addrs). To conform with the new close() behaviour we
>> are asserting the RTE_ETH_DEV_CLOSE_REMOVE flag so that
>> rte_eth_dev_close() releases all device level dynamic memory.
>>
>> Second level memory allocated to each individual rx/tx queue is now
>> freed as part of the close() operation therefore making it safe for the
>> rte_eth_dev_close() function to free the device private data without
>> orphaning the rx/tx queue pointers.
>>
>> Cc: Matt Peters <matt.peters@windriver.com>
>> Signed-off-by: Allain Legacy <allain.legacy@windriver.com>
>
> Acked-by: Matt Peters <matt.peters@windriver.com>
>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2019-06-25 17:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 19:18 Allain Legacy
2019-06-19 11:33 ` Peters, Matt
2019-06-25 17:27 ` 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=9c67c4e4-fa4f-6623-c0c8-157765e04ae1@intel.com \
--to=ferruh.yigit@intel.com \
--cc=Allain.Legacy@windriver.com \
--cc=Matt.Peters@windriver.com \
--cc=dev@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).