DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Jakub Grajciar <jgrajcia@cisco.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v12] eal_interrupts: add option for pending callback unregister
Date: Wed, 27 Mar 2019 19:01:09 +0100	[thread overview]
Message-ID: <2461195.sM7h6ISGy9@xps> (raw)
Message-ID: <20190327180109.LGNbhZbIZSZHGIPgxl23CiTlU5cGcfINHhb4kdrKce4@z> (raw)
In-Reply-To: <20190322115236.4189-1-jgrajcia@cisco.com>

22/03/2019 12:52, Jakub Grajciar:
> use case: if callback is used to receive message form socket,
> and the message received is disconnect/error, this callback needs
> to be unregistered, but cannot because it is still active.
> 
> With this patch it is possible to mark the callback to be
> unregistered once the interrupt process is done with this
> interrupt source.
> 
> Signed-off-by: Jakub Grajciar <jgrajcia@cisco.com>

Applied, thanks




  parent reply	other threads:[~2019-03-27 18:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-17 12:30 [dpdk-dev] [PATCH v8] " Jakub Grajciar
2019-01-14 14:01 ` Thomas Monjalon
2019-03-09  0:40 ` Thomas Monjalon
2019-03-20  9:26 ` [dpdk-dev] [PATCH v9] " Jakub Grajciar
2019-03-20  9:26   ` Jakub Grajciar
2019-03-21  9:23   ` [dpdk-dev] [PATCH v10] " Jakub Grajciar
2019-03-21  9:23     ` Jakub Grajciar
2019-03-21 10:08     ` [dpdk-dev] [PATCH v11] " Jakub Grajciar
2019-03-21 10:08       ` Jakub Grajciar
2019-03-22 11:52       ` [dpdk-dev] [PATCH v12] " Jakub Grajciar
2019-03-22 11:52         ` Jakub Grajciar
2019-03-27 18:01         ` Thomas Monjalon [this message]
2019-03-27 18:01           ` Thomas Monjalon

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=2461195.sM7h6ISGy9@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --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).