patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
To: "Min Hu (Connor)" <humin29@huawei.com>, dev@dpdk.org
Cc: stable@dpdk.org, Thomas Monjalon <thomas@monjalon.net>,
	Ferruh Yigit <ferruh.yigit@xilinx.com>,
	Anatoly Burakov <anatoly.burakov@intel.com>,
	Ajit Khaparde <ajit.khaparde@broadcom.com>
Subject: Re: [PATCH] ethdev: fix dev close in secondary process
Date: Tue, 31 May 2022 20:08:55 +0300	[thread overview]
Message-ID: <dae552a7-7d34-5347-5af5-9962aa6fee3e@oktetlabs.ru> (raw)
In-Reply-To: <20220527023553.48177-1-humin29@huawei.com>

On 5/27/22 05:35, Min Hu (Connor) wrote:
> From: Min Hu <humin29@huawei.com>
> 
> Shared memory like port private resources should only be reserved
> by primary process. Secondary process should not start dev, and
> the state of 'dev_started' is only meaningful to primary process.
> While secondary process need to close dev to release process private
> resources.
> 
> This patch limited the scope of 'dev_started'.

I agree with the patch since secondary process should not be
obliged to wait for device stop before closing ethdev. In any
case closing ethdev in secondary process should do nothing
harmful to the primary process.

However, the patch description pretends to limit dev_started
scope for secondary processes in general. It is wrong since
secondary processes need the information and that's why it is
stored in shared memory.

> 
> Fixes: febc855b358e ("ethdev: forbid closing started device")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Min Hu <humin29@huawei.com>
> ---
>   lib/ethdev/rte_ethdev.c | 3 ++-
>   1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/lib/ethdev/rte_ethdev.c b/lib/ethdev/rte_ethdev.c
> index 09abee6345..f34c6580a4 100644
> --- a/lib/ethdev/rte_ethdev.c
> +++ b/lib/ethdev/rte_ethdev.c
> @@ -1574,7 +1574,8 @@ rte_eth_dev_close(uint16_t port_id)
>   	RTE_ETH_VALID_PORTID_OR_ERR_RET(port_id, -ENODEV);
>   	dev = &rte_eth_devices[port_id];
>   
> -	if (dev->data->dev_started) {
> +	if (rte_eal_process_type() == RTE_PROC_PRIMARY &&
> +			dev->data->dev_started) {
>   		RTE_ETHDEV_LOG(ERR, "Cannot close started device (port %u)\n",
>   			       port_id);
>   		return -EINVAL;


  reply	other threads:[~2022-05-31 17:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-27  2:35 Min Hu (Connor)
2022-05-31 17:08 ` Andrew Rybchenko [this message]
2022-05-31 17:40   ` Stephen Hemminger
2022-06-01  1:33     ` Min Hu (Connor)

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=dae552a7-7d34-5347-5af5-9962aa6fee3e@oktetlabs.ru \
    --to=andrew.rybchenko@oktetlabs.ru \
    --cc=ajit.khaparde@broadcom.com \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@xilinx.com \
    --cc=humin29@huawei.com \
    --cc=stable@dpdk.org \
    --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).