From: Thomas Monjalon <thomas@monjalon.net>
To: Christophe Fontaine <cfontain@redhat.com>
Cc: Zhirun Yan <yanzhirun_163@163.com>,
dev@dpdk.org, Kiran Kumar Kokkilagadda <kirankumark@marvell.com>,
Nithin Kumar Dabilpuram <ndabilpuram@marvell.com>,
Guvenc Gulce <guvenc.gulce@gmail.com>,
Jerin Jacob <jerinj@marvell.com>
Subject: Re: [EXTERNAL] Re: [PATCH 0/2] graph: dispatch mode improvements
Date: Wed, 15 Oct 2025 21:59:58 +0200 [thread overview]
Message-ID: <17969458.Ash8RoxBsO@thomas> (raw)
In-Reply-To: <BY3PR18MB478556F4158B03FC20BB7A4BC81CA@BY3PR18MB4785.namprd18.prod.outlook.com>
24/09/2025 16:30, Jerin Jacob:
> From: Thomas Monjalon <thomas@monjalon.net>
> > 23/07/2025 18:49, Christophe Fontaine:
> > > Small series to improve dispatch mode for lib/graph.
> > > In order to run an instance of the graph in a control thread (slow
> > > path defined as nodes) in addition to the datapath thread, we need:
> > > - the ability to run graph_walk on an non-eal thread
> > > - a signaling mechanism to wake up the control thread
> >
> > Should I expect a review before merging? Someone?
>
> @Zhirun Yan The changes are for mcore dispatch, please review.
No news after 3 weeks.
> In general, changes looks good to me.
Applied, thanks.
prev parent reply other threads:[~2025-10-15 20:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 16:49 [PATCH 0/2] graph: dispatch mode improvements Christophe Fontaine
2025-07-23 16:50 ` [PATCH 1/2] graph: allow non EAL Thread for pipeline mode Christophe Fontaine
2025-07-23 16:50 ` [PATCH 2/2] graph: add callback in dispatch mode Christophe Fontaine
2025-09-24 14:18 ` [PATCH 0/2] graph: dispatch mode improvements Thomas Monjalon
2025-09-24 14:30 ` [EXTERNAL] " Jerin Jacob
2025-10-15 19:59 ` Thomas Monjalon [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=17969458.Ash8RoxBsO@thomas \
--to=thomas@monjalon.net \
--cc=cfontain@redhat.com \
--cc=dev@dpdk.org \
--cc=guvenc.gulce@gmail.com \
--cc=jerinj@marvell.com \
--cc=kirankumark@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=yanzhirun_163@163.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.