From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Junxiao Shi <git@mail1.yoursunny.com>, <dev@dpdk.org>
Cc: "Jakub Grajciar -X (jgrajcia - PANTHEON TECH SRO at Cisco)"
<jgrajcia@cisco.com>
Subject: Re: [PATCH] net/memif: allow stopping and closing device
Date: Wed, 24 Nov 2021 11:02:22 +0000 [thread overview]
Message-ID: <57a1f49b-8797-48ee-9ec7-2ec60ad5a042@intel.com> (raw)
In-Reply-To: <119df28c7cc9d267@cs.arizona.edu>
On 11/18/2021 5:33 PM, Junxiao Shi wrote:
> Bugzilla ID: 888
> Fixes: febc855b358e ("ethdev: forbid closing started device")
>
> Signed-off-by: Junxiao Shi <git@mail1.yoursunny.com>
Thanks Junxiao, +1 to this fix, cc'ed memif maintainer Jakub.
> ---
> drivers/net/memif/rte_eth_memif.c | 11 ++++++++---
> 1 file changed, 8 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/net/memif/rte_eth_memif.c b/drivers/net/memif/rte_eth_memif.c
> index 43d7378329..e3d523af57 100644
> --- a/drivers/net/memif/rte_eth_memif.c
> +++ b/drivers/net/memif/rte_eth_memif.c
> @@ -1260,6 +1260,13 @@ memif_dev_start(struct rte_eth_dev *dev)
> return ret;
> }
>
> +static int
> +memif_dev_stop(struct rte_eth_dev *dev)
> +{
> + memif_disconnect(dev);
Is the 'memif_dev_stop()' safe to be called multiple times?
If 'memif_dev_close()' calls 'memif_dev_stop()' (see below), it is possible
to call 'memif_dev_stop()' multiple times, so it should be protected.
> + return 0;
> +}
> +
> static int
> memif_dev_close(struct rte_eth_dev *dev)
> {
> @@ -1268,7 +1275,6 @@ memif_dev_close(struct rte_eth_dev *dev)
>
> if (rte_eal_process_type() == RTE_PROC_PRIMARY) {
> memif_msg_enq_disconnect(pmd->cc, "Device closed", 0);
> - memif_disconnect(dev);
>
> for (i = 0; i < dev->data->nb_rx_queues; i++)
> (*dev->dev_ops->rx_queue_release)(dev, i);
> @@ -1276,8 +1282,6 @@ memif_dev_close(struct rte_eth_dev *dev)
> (*dev->dev_ops->tx_queue_release)(dev, i);
>
> memif_socket_remove_device(dev);
> - } else {
> - memif_disconnect(dev);
Should we add 'memif_dev_stop()' within the close function?
Otherwise we are relying on user to stop, but at least in remove path
('rte_pmd_memif_remove()') that may not be the case.
> }
>
> rte_free(dev->process_private);
> @@ -1515,6 +1519,7 @@ memif_rx_queue_intr_disable(struct rte_eth_dev *dev, uint16_t qid __rte_unused)
>
> static const struct eth_dev_ops ops = {
> .dev_start = memif_dev_start,
> + .dev_stop = memif_dev_stop,
> .dev_close = memif_dev_close,
> .dev_infos_get = memif_dev_info,
> .dev_configure = memif_dev_configure,
>
next prev parent reply other threads:[~2021-11-24 11:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 17:33 Junxiao Shi
2021-11-24 11:02 ` Ferruh Yigit [this message]
2021-11-24 14:01 ` yoursunny
2021-11-24 14:43 ` Ferruh Yigit
2021-11-24 15:05 ` 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=57a1f49b-8797-48ee-9ec7-2ec60ad5a042@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=git@mail1.yoursunny.com \
--cc=jgrajcia@cisco.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).