From: Jerin Jacob <jerinjacobk@gmail.com>
To: Pavan Nikhilesh <pbhagavatula@marvell.com>
Cc: Jerin Jacob <jerinj@marvell.com>,
Anatoly Burakov <anatoly.burakov@intel.com>,
dpdk-dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] eventdev: fix device probe and remove for secondary process
Date: Fri, 1 May 2020 18:56:07 +0530 [thread overview]
Message-ID: <CALBAE1PxPQJBRegg27TGBbbLC4GqwmakrGT3fxZgZJCD+mifhA@mail.gmail.com> (raw)
In-Reply-To: <20200427181039.1943-1-pbhagavatula@marvell.com>
On Mon, Apr 27, 2020 at 11:40 PM <pbhagavatula@marvell.com> wrote:
>
> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
>
> When probing event device in secondary process skip reinitializing
> the device data structure as it is already done in primary process.
>
> When removing event device in secondary process skip closing the
> event device as it should be done by primary process.
>
> Fixes: 322d0345c2bc ("eventdev: implement PMD registration functions")
Cc: stable@dpdk.org
>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
Acked-by: Jerin Jacob <jerinj@marvell.com>
> ---
> lib/librte_eventdev/rte_eventdev.c | 13 ++++++++-----
> lib/librte_eventdev/rte_eventdev_pmd_pci.h | 8 +++++---
> 2 files changed, 13 insertions(+), 8 deletions(-)
>
> diff --git a/lib/librte_eventdev/rte_eventdev.c b/lib/librte_eventdev/rte_eventdev.c
> index b987e0745..9aca7fbd5 100644
> --- a/lib/librte_eventdev/rte_eventdev.c
> +++ b/lib/librte_eventdev/rte_eventdev.c
> @@ -1364,14 +1364,17 @@ rte_event_pmd_allocate(const char *name, int socket_id)
>
> eventdev->data = eventdev_data;
>
> - strlcpy(eventdev->data->name, name, RTE_EVENTDEV_NAME_MAX_LEN);
> + if (rte_eal_process_type() == RTE_PROC_PRIMARY) {
>
> - eventdev->data->dev_id = dev_id;
> - eventdev->data->socket_id = socket_id;
> - eventdev->data->dev_started = 0;
> + strlcpy(eventdev->data->name, name,
> + RTE_EVENTDEV_NAME_MAX_LEN);
>
> - eventdev->attached = RTE_EVENTDEV_ATTACHED;
> + eventdev->data->dev_id = dev_id;
> + eventdev->data->socket_id = socket_id;
> + eventdev->data->dev_started = 0;
> + }
>
> + eventdev->attached = RTE_EVENTDEV_ATTACHED;
> eventdev_globals.nb_devs++;
> }
>
> diff --git a/lib/librte_eventdev/rte_eventdev_pmd_pci.h b/lib/librte_eventdev/rte_eventdev_pmd_pci.h
> index 8fb61386f..443cd38c2 100644
> --- a/lib/librte_eventdev/rte_eventdev_pmd_pci.h
> +++ b/lib/librte_eventdev/rte_eventdev_pmd_pci.h
> @@ -112,9 +112,11 @@ rte_event_pmd_pci_remove(struct rte_pci_device *pci_dev,
> if (eventdev == NULL)
> return -ENODEV;
>
> - ret = rte_event_dev_close(eventdev->data->dev_id);
> - if (ret < 0)
> - return ret;
> + if (rte_eal_process_type() == RTE_PROC_PRIMARY) {
> + ret = rte_event_dev_close(eventdev->data->dev_id);
> + if (ret < 0)
> + return ret;
> + }
>
> /* Invoke PMD device un-init function */
> if (devuninit)
> --
> 2.17.1
>
next prev parent reply other threads:[~2020-05-01 13:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 18:10 pbhagavatula
2020-05-01 13:26 ` Jerin Jacob [this message]
2020-05-02 10:31 ` Jerin Jacob
2020-05-02 12:07 ` Varghese, Vipin
2020-05-02 13:04 ` Pavan Nikhilesh Bhagavatula
2020-05-03 1:15 ` Varghese, Vipin
2020-05-03 9:58 ` Jerin Jacob
2020-05-03 12:57 ` Varghese, Vipin
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=CALBAE1PxPQJBRegg27TGBbbLC4GqwmakrGT3fxZgZJCD+mifhA@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=pbhagavatula@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).