From: David Marchand <david.marchand@redhat.com>
To: Renata Saiakhova <Renata.Saiakhova@ekinops.com>
Cc: Anatoly Burakov <anatoly.burakov@intel.com>,
Harman Kalra <hkalra@marvell.com>,
Bruce Richardson <bruce.richardson@intel.com>,
Ray Kinsella <mdr@ashroe.eu>,
Neil Horman <nhorman@tuxdriver.com>, dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v4 1/1] eal/interrupts: add synchronous wrapper around unregister
Date: Thu, 25 Mar 2021 14:14:41 +0100 [thread overview]
Message-ID: <CAJFAV8xjtgre2ZGhQ4pm6QKDEv8wWNgCybWayc6Z=O9NumX=Aw@mail.gmail.com> (raw)
In-Reply-To: <20210218212746.3073-2-Renata.Saiakhova@ekinops.com>
On Thu, Feb 18, 2021 at 10:28 PM Renata Saiakhova
<Renata.Saiakhova@ekinops.com> wrote:
>
> Avoid race with unregister interrupt handler if interrupt
> source has some active callbacks at the moment, use wrapper
> around rte_intr_callback_unregister() to check for -EAGAIN
> return value and to loop until rte_intr_callback_unregister()
> succeeds.
>
> Signed-off-by: Renata Saiakhova <Renata.Saiakhova@ekinops.com>
> Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
> ---
> drivers/bus/pci/linux/pci_vfio.c | 2 +-
> lib/librte_eal/freebsd/eal_interrupts.c | 12 ++++++++++++
> lib/librte_eal/include/rte_interrupts.h | 25 +++++++++++++++++++++++++
> lib/librte_eal/linux/eal_interrupts.c | 12 ++++++++++++
> lib/librte_eal/version.map | 1 +
> 5 files changed, 51 insertions(+), 1 deletion(-)
Seeing the description of this function, I'd expect it to be the same
on all OS implementations.
Please, could you respin with Windows update?
[snip]
> diff --git a/lib/librte_eal/version.map b/lib/librte_eal/version.map
> index fce90a112..56caa9cc9 100644
> --- a/lib/librte_eal/version.map
> +++ b/lib/librte_eal/version.map
> @@ -318,6 +318,7 @@ EXPERIMENTAL {
> rte_fbarray_find_rev_biggest_free;
> rte_fbarray_find_rev_biggest_used;
> rte_intr_callback_unregister_pending;
> + rte_intr_callback_unregister_sync;
> rte_realloc_socket;
>
> # added in 19.08
> --
> 2.17.2
>
The new symbol should be with other 21.05 additions.
Thanks.
--
David Marchand
prev parent reply other threads:[~2021-03-25 13:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-18 21:27 [dpdk-dev] [PATCH v4 0/1] " Renata Saiakhova
2021-02-18 21:27 ` [dpdk-dev] [PATCH v4 1/1] " Renata Saiakhova
2021-03-11 9:44 ` [dpdk-dev] [EXT] " Harman Kalra
2021-03-25 13:14 ` David Marchand [this message]
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='CAJFAV8xjtgre2ZGhQ4pm6QKDEv8wWNgCybWayc6Z=O9NumX=Aw@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=Renata.Saiakhova@ekinops.com \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=hkalra@marvell.com \
--cc=mdr@ashroe.eu \
--cc=nhorman@tuxdriver.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).