DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: Liron Himi <lironh@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Liron Himi <lironh@marvell.com>
Subject: Re: [dpdk-dev] [PATCH] net/mvpp2: remove resources when port is closed
Date: Mon, 5 Aug 2019 17:28:51 +0000	[thread overview]
Message-ID: <BYAPR18MB24244420999A324578DB5C7BC8DA0@BYAPR18MB2424.namprd18.prod.outlook.com> (raw)
In-Reply-To: <1565000216-9465-1-git-send-email-lironh@marvell.com>

> -----Original Message-----
> From: lironh@marvell.com <lironh@marvell.com>
> Sent: Monday, August 5, 2019 3:47 PM
> To: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
> Cc: dev@dpdk.org; Liron Himi <lironh@marvell.com>
> Subject: [PATCH] net/mvpp2: remove resources when port is closed
> 
> From: Liron Himi <lironh@marvell.com>
> 
> Since 18.11, it is suggested that driver should release all its private resources
> at the dev_close routine. So all resources previously released in remove
> routine are now released at the dev_close routine, and the dev_close
> routine will be called in driver remove routine in order to support removing a
> device without closing its ports.
> 
> Above behavior changes are supported by setting
> RTE_ETH_DEV_CLOSE_REMOVE flag during probe stage.
> 
> Signed-off-by: Liron Himi <lironh@marvell.com>
> Reviewed-by: Yuri Chipchev <yuric@marvell.com>

Applied to dpdk-next-net-mrvl/master. Thanks

      reply	other threads:[~2019-08-05 17:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-05 10:16 lironh
2019-08-05 17:28 ` Jerin Jacob Kollanukkaran [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=BYAPR18MB24244420999A324578DB5C7BC8DA0@BYAPR18MB2424.namprd18.prod.outlook.com \
    --to=jerinj@marvell.com \
    --cc=dev@dpdk.org \
    --cc=lironh@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).