DPDK patches and discussions
 help / color / mirror / Atom feed
From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: Jerin Jacob <jerinjacobk@gmail.com>,
	Thomas Monjalon <thomas@monjalon.net>
Cc: dpdk-dev <dev@dpdk.org>,
	David Marchand <david.marchand@redhat.com>,
	Jerin Jacob <jerinj@marvell.com>,
	Andrew Rybchenko <arybchenko@solarflare.com>,
	 Ferruh Yigit <ferruh.yigit@intel.com>,
	Stephen Hemminger <stephen@networkplumber.org>,
	Ajit Khaparde <ajit.khaparde@broadcom.com>,
	Matan Azrad <matan@mellanox.com>,
	"John W. Linville" <linville@tuxdriver.com>,
	Qi Zhang <qi.z.zhang@intel.com>,
	Shepard Siegel <shepard.siegel@atomicrules.com>,
	Igor Russkikh <igor.russkikh@aquantia.com>,
	 Rasesh Mody <rmody@marvell.com>, Chas Williams <chas3@att.com>,
	Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>,
	Gagandeep Singh <G.Singh@nxp.com>,  Gaetan Rivet <grive@u256.net>,
	Cristian Dumitrescu <cristian.dumitrescu@intel.com>,
	"Wiles, Keith" <keith.wiles@intel.com>,
	Beilei Xing <beilei.xing@intel.com>,
	Jingjing Wu <jingjing.wu@intel.com>,
	Alfredo Cardigliano <cardigliano@ntop.org>,
	Rosen Xu <rosen.xu@intel.com>,
	Shijith Thotton <sthotton@marvell.com>,
	Heinrich Kuhn <heinrich.kuhn@netronome.com>
Subject: Re: [dpdk-dev] [PATCH] doc: announce ethdev port freeing on close operation
Date: Tue, 4 Aug 2020 09:29:15 +0000	[thread overview]
Message-ID: <AM6PR04MB44561E4C3E45CEDDC1012AC0894A0@AM6PR04MB4456.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <CALBAE1MOgEY++rmNzE-kKf0WXGOZ7nPggV_6UPXvJMhHLPejnQ@mail.gmail.com>

> On Tue, Aug 4, 2020 at 2:50 PM Thomas Monjalon <thomas@monjalon.net>
> wrote:
> >
> > 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>
> 
Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>

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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-04  9:20 Thomas Monjalon
2020-08-04  9:22 ` Jerin Jacob
2020-08-04  9:29   ` Hemant Agrawal [this message]
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=AM6PR04MB44561E4C3E45CEDDC1012AC0894A0@AM6PR04MB4456.eurprd04.prod.outlook.com \
    --to=hemant.agrawal@nxp.com \
    --cc=G.Singh@nxp.com \
    --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=grive@u256.net \
    --cc=heinrich.kuhn@netronome.com \
    --cc=igor.russkikh@aquantia.com \
    --cc=jerinj@marvell.com \
    --cc=jerinjacobk@gmail.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 \
    --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).