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>,
Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>,
Narcisa Ana Maria Vasile <navasile@linux.microsoft.com>,
Dmitry Malloy <dmitrym@microsoft.com>,
Pallavi Kadam <pallavi.kadam@intel.com>, dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v5 1/1] eal/interrupts: add synchronous wrapper around unregister
Date: Wed, 7 Apr 2021 11:12:01 +0200 [thread overview]
Message-ID: <CAJFAV8yWRPQ2jeRs=bOgkO9zfaV92qLavhqx=_HDJd2e=+cB4Q@mail.gmail.com> (raw)
In-Reply-To: <20210406144614.3394-2-Renata.Saiakhova@ekinops.com>
On Tue, Apr 6, 2021 at 4:50 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>
> Acked-by: Harman Kalra <hkalra@marvell.com>
> ---
[snip]
> diff --git a/lib/librte_eal/version.map b/lib/librte_eal/version.map
> index e23745ae6..88d88aaed 100644
> --- a/lib/librte_eal/version.map
> +++ b/lib/librte_eal/version.map
> @@ -421,6 +421,7 @@ EXPERIMENTAL {
> rte_version_release;
> rte_version_suffix;
> rte_version_year;
> + rte_intr_callback_unregister_sync;
Sorted this alphabetically + added symbol in rte_eal_exports.def.
Applied, thanks.
--
David Marchand
prev parent reply other threads:[~2021-04-07 9:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 14:46 [dpdk-dev] [PATCH v5 0/1] " Renata Saiakhova
2021-04-06 14:46 ` [dpdk-dev] [PATCH v5 1/1] " Renata Saiakhova
2021-04-07 9:12 ` 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='CAJFAV8yWRPQ2jeRs=bOgkO9zfaV92qLavhqx=_HDJd2e=+cB4Q@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=dmitry.kozliuk@gmail.com \
--cc=dmitrym@microsoft.com \
--cc=hkalra@marvell.com \
--cc=mdr@ashroe.eu \
--cc=navasile@linux.microsoft.com \
--cc=nhorman@tuxdriver.com \
--cc=pallavi.kadam@intel.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).