From: Harman Kalra <hkalra@marvell.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: <stephen@networkplumber.org>, <jgrajcia@cisco.com>,
<david.marchand@redhat.com>, <dev@dpdk.org>, <stable@dpdk.org>
Subject: Re: [dpdk-dev] [EXT] Re: [PATCH] eal: fix epoll fd list rebuild
Date: Mon, 25 May 2020 15:19:08 +0530 [thread overview]
Message-ID: <20200525094845.GA54610@outlook.office365.com> (raw)
In-Reply-To: <2674031.7s9Q9pJsto@thomas>
On Sun, May 24, 2020 at 05:30:26PM +0200, Thomas Monjalon wrote:
> External Email
>
> ----------------------------------------------------------------------
> 11/05/2020 15:43, Harman Kalra:
> > An issue has been observed where epoll file descriptor
> > list rebuilds every time an interrupt/alarm event is
> > received.
> >
> > eal_intr_process_interrupts() should notify pipe fd only
> > if any source is removed from the source list i.e (rv > 0)
> >
> > Fixes: 0c7ce182a760 ("eal: add pending interrupt callback unregister"
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Harman Kalra <hkalra@marvell.com>
>
> This patch is missing 20.05 because no review was done.
> In general, we are missing a maintainer on "interrupts" area.
Hi Thomas,
If everybody is fine we can take up the responsibility of maintaining
interrupt subsystem. I can send a patch to update maintainer list for
the same.
Thanks
Harman
>
>
next prev parent reply other threads:[~2020-05-25 9:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 13:43 [dpdk-dev] " Harman Kalra
2020-05-24 15:30 ` Thomas Monjalon
2020-05-25 9:49 ` Harman Kalra [this message]
2020-05-27 12:32 ` [dpdk-dev] [EXT] " Harman Kalra
2020-05-27 12:44 ` Harman Kalra
2020-05-27 13:04 ` Thomas Monjalon
2020-05-27 17:19 ` Harman Kalra
2020-06-19 13:59 ` [dpdk-dev] [PATCH v2] " Harman Kalra
2020-06-24 8: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=20200525094845.GA54610@outlook.office365.com \
--to=hkalra@marvell.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jgrajcia@cisco.com \
--cc=stable@dpdk.org \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
/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).