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>,
"Yuri Chipchev" <yuric@marvell.com>,
Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH] net/mvneta: remove resources when port is closed
Date: Sun, 7 Jul 2019 10:25:38 +0000 [thread overview]
Message-ID: <BYAPR18MB2424421625915391F4D07AF1C8F70@BYAPR18MB2424.namprd18.prod.outlook.com> (raw)
In-Reply-To: <1562140692-309-1-git-send-email-lironh@marvell.com>
> -----Original Message-----
> From: lironh@marvell.com <lironh@marvell.com>
> Sent: Wednesday, July 3, 2019 1:28 PM
> To: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
> Cc: dev@dpdk.org; Liron Himi <lironh@marvell.com>; Yuri Chipchev
> <yuric@marvell.com>
> Subject: [PATCH] net/mvneta: remove resources when port is closed
>
> From: yuric <yuric@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: yuric <yuric@marvell.com>
> Reviewed-by: Liron Himi <lironh@marvell.com>
Applied to dpdk-next-net-mrvl/master. Thanks
next prev parent reply other threads:[~2019-07-07 10:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-03 7:58 lironh
2019-07-07 10:25 ` Jerin Jacob Kollanukkaran [this message]
2019-07-08 16:12 ` Ferruh Yigit
2019-07-08 18:50 ` Liron Himi
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=BYAPR18MB2424421625915391F4D07AF1C8F70@BYAPR18MB2424.namprd18.prod.outlook.com \
--to=jerinj@marvell.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=lironh@marvell.com \
--cc=yuric@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).