From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
To: Thomas Monjalon <thomas@monjalon.net>,
Ivan Ilchenko <ivan.ilchenko@oktetlabs.ru>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>,
dev@dpdk.org, Maxime Coquelin <maxime.coquelin@redhat.com>,
Chenbo Xia <chenbo.xia@intel.com>
Subject: Re: [dpdk-dev] [PATCH] ethdev: stop the device before close
Date: Wed, 20 Oct 2021 15:24:07 +0300 [thread overview]
Message-ID: <31d69964-1b54-ce9e-b917-9ab6f86571b7@oktetlabs.ru> (raw)
In-Reply-To: <2158870.PWGGICSfzm@thomas>
On 10/20/21 3:17 PM, Thomas Monjalon wrote:
> 20/10/2021 12:47, Andrew Rybchenko:
>> From: Ivan Ilchenko <ivan.ilchenko@oktetlabs.ru>
>>
>> In drivers important cleanup could happen on the device stop.
>> Do stop in the rte_eth_dev_close() function for robustness and
>> to simplify drivers code.
>>
>> Signed-off-by: Ivan Ilchenko <ivan.ilchenko@oktetlabs.ru>
>> Signed-off-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
>> ---
>> In fact the patch is required to fix segfault in the case of
>> net/virtio on close without stop after Rx interrupts enabled.
>>
>> I believe that the right way to address the problem is automated
>> stop from close, but I guess it cannot not be backported and
>> may be fix in a different way required in stable branches.
>
> It is possible to do this addition.
> But the right fix (not changing API behaviour) should be to return early
> if the port is not stopped.
Isn't returning an error a change of API behaviour?
This way we change behaviour less since some PMDs allow
to close in started state and do stop itself.
>
>> @@ -1894,6 +1894,17 @@ rte_eth_dev_close(uint16_t port_id)
>> dev = &rte_eth_devices[port_id];
>>
>> RTE_FUNC_PTR_OR_ERR_RET(*dev->dev_ops->dev_close, -ENOTSUP);
>> +
>> + if (dev->data->dev_started) {
>> + *lasterr = rte_eth_dev_stop(port_id);
>> + if (*lasterr != 0) {
>> + RTE_ETHDEV_LOG(ERR,
>> + "Failed to stop device (port %u) before close: %s - ignore\n",
>> + port_id, rte_strerror(-*lasterr));
>> + lasterr = &binerr;
>> + }
>> + }
>> +
>> *lasterr = (*dev->dev_ops->dev_close)(dev);
>> if (*lasterr != 0)
>> lasterr = &binerr;
>
>
next prev parent reply other threads:[~2021-10-20 12:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 10:47 Andrew Rybchenko
2021-10-20 12:17 ` Thomas Monjalon
2021-10-20 12:24 ` Andrew Rybchenko [this message]
2021-10-20 13:06 ` Andrew Rybchenko
2021-10-20 13:15 ` [dpdk-dev] [PATCH v2] ethdev: do not allow to close started device Andrew Rybchenko
2021-10-20 13:36 ` Thomas Monjalon
2021-10-20 16:22 ` Ajit Khaparde
2021-10-20 17:25 ` Ferruh Yigit
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=31d69964-1b54-ce9e-b917-9ab6f86571b7@oktetlabs.ru \
--to=andrew.rybchenko@oktetlabs.ru \
--cc=chenbo.xia@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=ivan.ilchenko@oktetlabs.ru \
--cc=maxime.coquelin@redhat.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).