DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: david.marchand@redhat.com, jerinj@marvell.com,
	arybchenko@solarflare.com, ferruh.yigit@intel.com,
	stephen@networkplumber.org, ajit.khaparde@broadcom.com,
	matan@mellanox.com, linville@tuxdriver.com, qi.z.zhang@intel.com,
	shepard.siegel@atomicrules.com, igor.russkikh@aquantia.com,
	rmody@marvell.com, chas3@att.com, rahul.lakkireddy@chelsio.com,
	hemant.agrawal@nxp.com, g.singh@nxp.com, grive@u256.net,
	cristian.dumitrescu@intel.com, keith.wiles@intel.com,
	beilei.xing@intel.com, jingjing.wu@intel.com,
	cardigliano@ntop.org, rosen.xu@intel.com, sthotton@marvell.com,
	heinrich.kuhn@netronome.com
Subject: [dpdk-dev] [PATCH] doc: announce ethdev port freeing on close operation
Date: Tue,  4 Aug 2020 11:20:14 +0200	[thread overview]
Message-ID: <20200804092014.3335076-1-thomas@monjalon.net> (raw)

Since DPDK 18.11, some drivers are migrating to a new behaviour,
releasing port resources on close.
The temporary flag RTE_ETH_DEV_CLOSE_REMOVE triggers this new mode
in the migrated drivers.
After 2 years, the flag and the old behaviour will be removed.
Last drivers not migrated will have to complete the switch.

Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---
 doc/guides/rel_notes/deprecation.rst | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index ea4cfa7a48..b5e8045d00 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -91,6 +91,12 @@ Deprecation Notices
   - ``rte_eth_dev_stop``
   - ``rte_eth_dev_close``
 
+* ethdev: The temporary flag RTE_ETH_DEV_CLOSE_REMOVE will be removed in 20.11.
+  As a consequence, the new behaviour introduced in 18.11 will be effective
+  for all drivers: generic port resources are freed on close operation.
+  Private resources are expected to be released in the ``dev_close`` callback.
+  More details in http://inbox.dpdk.org/dev/5248162.j6AOsuQRmx@thomas/
+
 * ethdev: New offload flags ``DEV_RX_OFFLOAD_FLOW_MARK`` will be added in 19.11.
   This will allow application to enable or disable PMDs from updating
   ``rte_mbuf::hash::fdir``.
-- 
2.27.0


             reply	other threads:[~2020-08-04  9:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-04  9:20 Thomas Monjalon [this message]
2020-08-04  9:22 ` Jerin Jacob
2020-08-04  9:29   ` Hemant Agrawal
2020-08-04 17:34     ` Ajit Khaparde
2020-08-05 10:33       ` Andrew Rybchenko
2020-08-06  0:18         ` Thomas Monjalon

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=20200804092014.3335076-1-thomas@monjalon.net \
    --to=thomas@monjalon.net \
    --cc=ajit.khaparde@broadcom.com \
    --cc=arybchenko@solarflare.com \
    --cc=beilei.xing@intel.com \
    --cc=cardigliano@ntop.org \
    --cc=chas3@att.com \
    --cc=cristian.dumitrescu@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=g.singh@nxp.com \
    --cc=grive@u256.net \
    --cc=heinrich.kuhn@netronome.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=igor.russkikh@aquantia.com \
    --cc=jerinj@marvell.com \
    --cc=jingjing.wu@intel.com \
    --cc=keith.wiles@intel.com \
    --cc=linville@tuxdriver.com \
    --cc=matan@mellanox.com \
    --cc=qi.z.zhang@intel.com \
    --cc=rahul.lakkireddy@chelsio.com \
    --cc=rmody@marvell.com \
    --cc=rosen.xu@intel.com \
    --cc=shepard.siegel@atomicrules.com \
    --cc=stephen@networkplumber.org \
    --cc=sthotton@marvell.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).