From: Jerin Jacob <jerinjacobk@gmail.com>
To: "Mattias Rönnblom" <hofors@lysator.liu.se>
Cc: "Pravin Pathak" <pravin.pathak@intel.com>,
dev@dpdk.org, jerinj@marvell.com, mike.ximing.chen@intel.com,
bruce.richardson@intel.com, thomas@monjalon.net,
david.marchand@redhat.com, nipun.gupta@amd.com,
chenbox@nvidia.com, tirthendu.sarkar@intel.com,
"Pavan Nikhilesh" <pbhagavatula@marvell.com>,
"Shijith Thotton" <sthotton@marvell.com>,
"Hemant Agrawal" <hemant.agrawal@nxp.com>,
"Sachin Saxena" <sachin.saxena@oss.nxp.com>,
harry.chang@intel.com,
"Mattias Rönnblom" <mattias.ronnblom@ericsson.com>
Subject: Re: [PATCH v1] event/dlb2: add dequeue interrupt mode support
Date: Mon, 30 Jun 2025 17:13:57 +0530 [thread overview]
Message-ID: <CALBAE1MUrpZqWA=E78QiWy7k=H8QrYQ-=4vme4eHqSm8avBHJg@mail.gmail.com> (raw)
In-Reply-To: <bc0299d2-052d-4188-ab18-987360d65cb4@lysator.liu.se>
On Mon, Jun 30, 2025 at 4:47 PM Mattias Rönnblom <hofors@lysator.liu.se> wrote:
>
> On 2025-06-30 11:19, Jerin Jacob wrote:
> > On Sat, Jun 28, 2025 at 11:17 AM Pravin Pathak <pravin.pathak@intel.com> wrote:
> >>
> >> DLB2 port interrupt is implemented using DPDK interrupt
> >> framework. This allows eventdev dequeue API to sleep when
> >> the port queue is empty and gets wakeup when event arrives
> >> at the port. Port dequeue mode is configured using devargs
> >> argument port_dequeue_wait. Supported modes are polling and
> >> interrupt. Default mode is polling.
> >> This commit also adds code to handle device error interrupts
> >> and print alarm details.
> >>
> >> Signed-off-by: Pravin Pathak <pravin.pathak@intel.com>
> >> Signed-off-by: Tirthendu Sarkar <tirthendu.sarkar@intel.com>
> >> ---
> >> doc/guides/eventdevs/dlb2.rst | 20 +
> >> drivers/event/dlb2/dlb2.c | 236 +++++-
> >> drivers/event/dlb2/dlb2_iface.c | 7 +
> >> drivers/event/dlb2/dlb2_iface.h | 8 +
> >> drivers/event/dlb2/dlb2_priv.h | 18 +
> >> drivers/event/dlb2/dlb2_user.h | 112 +++
> >> drivers/event/dlb2/pf/base/dlb2_hw_types.h | 70 ++
> >> drivers/event/dlb2/pf/base/dlb2_osdep.h | 46 ++
> >> drivers/event/dlb2/pf/base/dlb2_regs.h | 149 +++-
> >> drivers/event/dlb2/pf/base/dlb2_resource.c | 825 +++++++++++++++++++++
> >> drivers/event/dlb2/pf/base/dlb2_resource.h | 6 +
> >> drivers/event/dlb2/pf/dlb2_pf.c | 223 ++++++
> >> 12 files changed, 1711 insertions(+), 9 deletions(-)
> >>
> >> diff --git a/doc/guides/eventdevs/dlb2.rst b/doc/guides/eventdevs/dlb2.rst
> >> index 8ec7168f20..a4ba857351 100644
> >> --- a/doc/guides/eventdevs/dlb2.rst
> >> +++ b/doc/guides/eventdevs/dlb2.rst
> >> @@ -477,6 +477,26 @@ Example command to use as meson option for credit handling:
> >>
> >> meson configure -Dc_args='-DDLB_SW_CREDITS_CHECKS=0 -DDLB_HW_CREDITS_CHECKS=1'
> >>
> >> +Interrupt Mode Support
> >> +~~~~~~~~~~~~~~~~~~~~~~
> >> +DLB dequeue supports interrupt mode for the API rte_event_dequeue_burst().
> >> +The default port dequeue mode is polling. Dequeue wait mode can be configured
> >> +on per eventdev port basis using devargs argument 'port_dequeue_wait'. In
> >> +interrupt mode, if the port queue is empty, the application thread will block
> >> +on the interrupt until a new event arrives. It enters blocking mode only after
> >> +any specified timeout. During the timeout, it will poll the port queue for
> >> +events as usual. Interrupt mode uses the DPDK interrupt support framework.
> >> +
> >> + .. code-block:: console
> >> +
> >> + --allow ea:00.0,port_dequeue_wait=all:interrupt
> >
> > Adding other eventdev PMD mainatainers.
> >
> > Looks like it can be a generic feature. i.e set this option is dev_configure()
> > If there is no objection, Please send a new patch around that.
>
> I've considered implementing this in DSW, although in a different manner
> (with eventfds and poll()).
>
> The dequeue timeout will still be honored in "interrupt mode", correct?
> It wasn't obvious from the description.
How is it in Intel PMD?
>
> What's being configured should just be a threshold time at which the
> event device would go from busy-polling to blocking the thread.
>
> Maybe it should be called something with "blocking" or "sleeping",
> instead of "interrupt", since interrupts are never directly involved.
Agree. or make it a power save mode or so.
>
> Anyway, seems like a good candidate for a generic feature to me.
>
next prev parent reply other threads:[~2025-06-30 11:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-28 4:51 Pravin Pathak
2025-06-30 2:25 ` [PATCH v2] " Pravin Pathak
2025-06-30 9:19 ` [PATCH v1] " Jerin Jacob
2025-06-30 11:17 ` Mattias Rönnblom
2025-06-30 11:43 ` Jerin Jacob [this message]
2025-06-30 16:18 ` Pathak, Pravin
2025-06-30 16:22 ` Jerin Jacob
2025-06-30 16:51 ` Mattias Rönnblom
2025-06-30 17:34 ` Pathak, Pravin
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='CALBAE1MUrpZqWA=E78QiWy7k=H8QrYQ-=4vme4eHqSm8avBHJg@mail.gmail.com' \
--to=jerinjacobk@gmail.com \
--cc=bruce.richardson@intel.com \
--cc=chenbox@nvidia.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=harry.chang@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=hofors@lysator.liu.se \
--cc=jerinj@marvell.com \
--cc=mattias.ronnblom@ericsson.com \
--cc=mike.ximing.chen@intel.com \
--cc=nipun.gupta@amd.com \
--cc=pbhagavatula@marvell.com \
--cc=pravin.pathak@intel.com \
--cc=sachin.saxena@oss.nxp.com \
--cc=sthotton@marvell.com \
--cc=thomas@monjalon.net \
--cc=tirthendu.sarkar@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).