From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Michal Krawczyk <mk@semihalf.com>,
mw@semihalf.com, matua@amazon.com, gtzalik@amazon.com,
zorik@amazon.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] net/ena: remove resources when port is being closed
Date: Fri, 2 Nov 2018 20:35:59 +0000 [thread overview]
Message-ID: <a4e75429-7c57-333f-b974-39d4eee844a2@intel.com> (raw)
In-Reply-To: <20181031145316.7448-1-mk@semihalf.com>
On 10/31/2018 2:53 PM, Michal Krawczyk wrote:
> The new API introduced in 18.11 is suggesting, that the driver should
> release all it's resources at the dev_close routine.
>
> All resources previously released in uninit routine during PCI removal,
> are now being released at the dev_close and the PMD is indicating that
> it is supporting API changes by setting RTE_ETH_DEV_CLOSE_REMOVE flag.
>
> As the device is not allocating MAC addresses dynamically, it is setting
> mac_addrs field to NULL, so it wouldn't be released by the
> rte_eth_dev_release_port().
>
> Signed-off-by: Michal Krawczyk <mk@semihalf.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2018-11-02 20:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 14:53 Michal Krawczyk
2018-11-02 20:35 ` 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=a4e75429-7c57-333f-b974-39d4eee844a2@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=gtzalik@amazon.com \
--cc=matua@amazon.com \
--cc=mk@semihalf.com \
--cc=mw@semihalf.com \
--cc=zorik@amazon.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).