From: Jerin Jacob <jerinj@marvell.com>
To: Thomas Monjalon <thomas@monjalon.net>,
Christophe Fontaine <cfontain@redhat.com>,
Zhirun Yan <yanzhirun_163@163.com>
Cc: Kiran Kumar Kokkilagadda <kirankumark@marvell.com>,
Nithin Kumar Dabilpuram <ndabilpuram@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Guvenc Gulce <guvenc.gulce@gmail.com>
Subject: RE: [EXTERNAL] Re: [PATCH 0/2] graph: dispatch mode improvements
Date: Wed, 24 Sep 2025 14:30:04 +0000 [thread overview]
Message-ID: <BY3PR18MB478556F4158B03FC20BB7A4BC81CA@BY3PR18MB4785.namprd18.prod.outlook.com> (raw)
In-Reply-To: <2836217.eGJsNajkDb@thomas>
> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Wednesday, September 24, 2025 7:49 PM
> To: Christophe Fontaine <cfontain@redhat.com>
> Cc: Jerin Jacob <jerinj@marvell.com>; Kiran Kumar Kokkilagadda
> <kirankumark@marvell.com>; Nithin Kumar Dabilpuram
> <ndabilpuram@marvell.com>; Zhirun Yan <yanzhirun_163@163.com>;
> dev@dpdk.org; Guvenc Gulce <guvenc.gulce@gmail.com>
> Subject: [EXTERNAL] Re: [PATCH 0/2] graph: dispatch mode improvements
>
> 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: ZjQcmQRYFpfptBannerStart Prioritize security for external emails:
> Confirm sender and content safety before clicking links or opening attachments
> <https://us-phishalarm-
> ewt.proofpoint.com/EWT/v1/CRVmXkqW!s03Z1P80YjX6F8USVpU1pEPnEL9aBV
> CDmZhTUwMWrUFrDQFePMFjzqQsmmFOvE8V7-Hk$>
> Report Suspicious
>
> ZjQcmQRYFpfptBannerEnd
> 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.
In general, changes looks good to me.
>
prev parent reply other threads:[~2025-09-24 14:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 16:49 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 ` Jerin Jacob [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=BY3PR18MB478556F4158B03FC20BB7A4BC81CA@BY3PR18MB4785.namprd18.prod.outlook.com \
--to=jerinj@marvell.com \
--cc=cfontain@redhat.com \
--cc=dev@dpdk.org \
--cc=guvenc.gulce@gmail.com \
--cc=kirankumark@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=thomas@monjalon.net \
--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 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).