DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Heinrich Kuhn <heinrich.kuhn@netronome.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 0/2] free port private data in dev_close callback
Date: Wed, 27 Jan 2021 22:45:36 +0000	[thread overview]
Message-ID: <cd7c1d3b-29a1-d38e-fda3-1b12e2a899a7@intel.com> (raw)
In-Reply-To: <20210119115616.1807-1-heinrich.kuhn@netronome.com>

On 1/19/2021 11:56 AM, Heinrich Kuhn wrote:
> The first patch in this series prepares the NFP PMD for the new expected
> behavior of the .dev_close() callback function, most recently described
> in commit fbd191356148 ("ethdev: remove old close behaviour"). Patch one
> makes the needed infrastructure changes to make this possible.
> 
> The second patch in the series makes the changes in nfp_net_close to
> free the private data of a given port. PF resources are only freed once
> all other ports under the PF has also been cleaned up.
> 
> Heinrich Kuhn (2):
>    net/nfp: create a separate entity for a NFP PF device
>    net/nfp: free port private data in dev close callback
> 

Thanks for the update.

Series applied to dpdk-next-net/main, thanks.

      parent reply	other threads:[~2021-01-27 22:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-19 11:56 Heinrich Kuhn
2021-01-19 11:56 ` [dpdk-dev] [PATCH 1/2] net/nfp: create a separate entity for a NFP PF device Heinrich Kuhn
2021-01-19 11:56 ` [dpdk-dev] [PATCH 2/2] net/nfp: free port private data in dev close callback Heinrich Kuhn
2021-01-27 22:45 ` 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=cd7c1d3b-29a1-d38e-fda3-1b12e2a899a7@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=heinrich.kuhn@netronome.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).