From: "Robin Jarry" <rjarry@redhat.com>
To: "Jerin Jacob" <jerinj@marvell.com>, "dev@dpdk.org" <dev@dpdk.org>,
"Kiran Kumar Kokkilagadda" <kirankumark@marvell.com>,
"Nithin Kumar Dabilpuram" <ndabilpuram@marvell.com>,
"Zhirun Yan" <yanzhirun_163@163.com>
Cc: "Vladimir Medvedkin" <vladimir.medvedkin@intel.com>,
"Christophe Fontaine" <cfontain@redhat.com>,
"David Marchand" <david.marchand@redhat.com>,
"Konstantin Ananyev" <konstantin.ananyev@huawei.com>,
"Maxime Leroy" <maxime@leroys.fr>
Subject: Re: [EXTERNAL] [PATCH dpdk] graph: replace circular buffer with priority-based bitmap scheduling
Date: Tue, 19 May 2026 23:32:56 +0200 [thread overview]
Message-ID: <DIMZ41ANY5TQ.3SXX22QGRY92R@redhat.com> (raw)
In-Reply-To: <PH7PR18MB507823DB7B8D54E605C4437CC8002@PH7PR18MB5078.namprd18.prod.outlook.com>
Hi Jerin,
Jerin Jacob, May 19, 2026 at 12:25:
> Some high-level comments:
>
> 1)What will be the performance overhead for graph walk. Try
> app/test/test_graph_perf.c and l3fwd_graph
I have made some measurements. There was a regression caused by
systematic access to a cache line. This will be fixed in v2.
> 2)If priorities are same, Does it have similar performance with
> existing code?
Yes with v2. I have added a topo order as a fallback when all priorities
are equal so that it behaves as previously.
> 3)Does it have any effect on packet ordering on egress.i.e for a given
> flow ingress order != egress order
Some independent flows "may" be reordered but that depends on the
topology, not the graph walk algorithm.
For example, the following graph:
+--------+
| eth_in |
+--------+
/ \
v v
+-------+ +---------+
| ip_in | <-- | mpls_in |
+-------+ +---------+
|
| ,------------.
v v |
+--------+ +----------+
| ip_out | --> | ipip_out |
+--------+ +----------+
|
v
+---------+
| eth_out |
+---------+
If you receive the following stream of packets in "eth_in":
1. Eth/IP
2. Eth/IP
3. Eth/MPLS/IP
4. Eth/MPLS/IP
5. Eth/MPLS/IP
6. Eth/IP (needs IPIP encap)
7. Eth/IP (needs IPIP encap)
8. Eth/IP
The "eth_out" node will see:
1. Eth/IP
2. Eth/IP
3. Eth/IP
4. Eth/IP
5. Eth/IP
* 8. Eth/IP <----------- reordered before 6 and 7
6. Eth/IP/IP
7. Eth/IP/IP
With the FIFO circular buffer and with the new bitmap priority scheduler.
The only difference with the bitmap system is that If you set "mpls_in"
and "ip_out" higher priorities, the "ip_in" and "eth_out" nodes will be
visited only once.
> If there is performance regression we may need to consider new
> RTE_GRAPH_MODEL_XXXXX to enable this feature
--
Robin
> Times approximate.
next prev parent reply other threads:[~2026-05-19 21:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 10:12 [PATCH dpdk] graph: replace circular buffer with priority-based bitmap scheduling Robin Jarry
2026-05-19 10:25 ` [EXTERNAL] " Jerin Jacob
2026-05-19 21:32 ` Robin Jarry [this message]
2026-06-09 4:52 ` Jerin Jacob
2026-05-19 21:38 ` [PATCH dpdk v2 0/2] graph: " Robin Jarry
2026-05-19 21:38 ` [PATCH dpdk v2 1/2] graph: add diamond topology performance test Robin Jarry
2026-05-19 21:38 ` [PATCH dpdk v2 2/2] graph: replace circular buffer with priority-based bitmap Robin Jarry
2026-06-16 6:30 ` kirankumark
2026-06-16 7:16 ` Robin Jarry
2026-06-16 7:57 ` kirankumark
2026-06-16 8:03 ` kirankumark
2026-06-10 10:51 ` [EXTERNAL] [PATCH dpdk] graph: replace circular buffer with priority-based bitmap scheduling Kiran Kumar Kokkilagadda
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=DIMZ41ANY5TQ.3SXX22QGRY92R@redhat.com \
--to=rjarry@redhat.com \
--cc=cfontain@redhat.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=kirankumark@marvell.com \
--cc=konstantin.ananyev@huawei.com \
--cc=maxime@leroys.fr \
--cc=ndabilpuram@marvell.com \
--cc=vladimir.medvedkin@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox