From: Jerin Jacob <jerinjacobk@gmail.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Sunil Kumar Kori <skori@marvell.com>,
Rakesh Kudurumalla <rkudurumalla@marvell.com>,
jerinj@marvell.com, dev@dpdk.org, ndabilpuram@marvell.com
Subject: Re: [PATCH v10 3/3] app/graph: implement port forward usecase
Date: Mon, 19 Feb 2024 08:44:07 +0530 [thread overview]
Message-ID: <CALBAE1ORQg_ai0cSdnFSU-15doOvbOT++RePUF7YR6o3mGmRkQ@mail.gmail.com> (raw)
In-Reply-To: <8163802.tM3a2QDmDi@thomas>
On Mon, Feb 19, 2024 at 4:00 AM Thomas Monjalon <thomas@monjalon.net> wrote:
>
> 02/01/2024 08:30, Rakesh Kudurumalla:
> > --- /dev/null
> > +++ b/doc/guides/tools/img/graph-usecase-l2fwd.svg
> > @@ -0,0 +1,92 @@
> > +<?xml version="1.0" encoding="UTF-8" standalone="no"?>
> > +<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN"
> > + "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
> > +<!-- Generated by graphviz version 2.43.0 (0)
> > + -->
> > +<!-- SPDX-License-Identifier: BSD-3-Clause -->
> > +<!-- Copyright(C) 2023 Marvell. -->
> > +<!--
> > +
> > +Generated with following command
> > +dot -Tsvg dot.dot -o doc/guides/tools/img/graph-usecase-l2fwd.svg
> > +
> > +cat dot.dot
> > +digraph dpdk_app_graph_l2fwd_nodes_flow {
> > + ingress_port [shape=rect]
> > + ethdev_rx
> > + ethdev_tx
> > + pkt_drop
> > + egress_port [shape=rect]
> > +
> > + ingress_port -> ethdev_rx [label="ingress packet"]
> > +
> > + ethdev_rx -> ethdev_tx
> > + ethdev_tx -> egress_port [label="egress packet"]
> > + ethdev_tx -> pkt_drop [color="red" style="dashed"]
> > +}
> > + -->
>
> We could include this syntax directly in .rst file
> with this Sphinx extension:
> https://www.sphinx-doc.org/en/master/usage/extensions/graphviz.html
I checked that option earlier. Created this scheme to avoid graphviz
package dependency
to DPDK.
commit 597f51c34826b3b12b6a1ac9d54e9160aaa49ef7
Author: Jerin Jacob <jerinj@marvell.com>
Date: Fri Jun 23 13:06:00 2023 +0530
doc: add inbuilt graph nodes data flow
Added diagram to depict the data flow between inbuilt
graph nodes.
In order to avoid graphviz package dependency to DPDK
documentation, manual step added to create a svg file
from the dot file. The details for the same is documented
in graph_inbuilt_node_flow.svg as a comment.
Signed-off-by: Jerin Jacob <jerinj@marvell.com>
Reviewed-by: Zhirun Yan <zhirun.yan@intel.com>
>
>
>
next prev parent reply other threads:[~2024-02-19 3:14 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 6:15 [PATCH 1/2] node: forward packet from ethdev_rx node Rakesh Kudurumalla
2023-11-23 6:15 ` [PATCH 2/2] app/graph: implement L2FWD usecase Rakesh Kudurumalla
2023-11-24 8:13 ` Sunil Kumar Kori
2023-11-24 7:45 ` [EXT] [PATCH 1/2] node: forward packet from ethdev_rx node Sunil Kumar Kori
2023-12-04 18:04 ` [PATCH v2 1/3] node: support to add next node to ethdev Rx node Rakesh Kudurumalla
2023-12-04 18:04 ` [PATCH v2 2/3] app/graph: add ethdev forward command Rakesh Kudurumalla
2023-12-04 18:04 ` [PATCH v2 3/3] app/graph: implement port forward usecase Rakesh Kudurumalla
2023-12-05 7:46 ` [PATCH v3 1/3] node: support to add next node to ethdev Rx node Rakesh Kudurumalla
2023-12-05 7:46 ` [PATCH v3 2/3] app/graph: add ethdev forward command Rakesh Kudurumalla
2023-12-05 7:46 ` [PATCH v3 3/3] app/graph: implement port forward usecase Rakesh Kudurumalla
2023-12-05 9:27 ` [PATCH v4 1/3] node: support to add next node to ethdev Rx node Rakesh Kudurumalla
2023-12-05 9:27 ` [PATCH v4 2/3] app/graph: add ethdev forward command Rakesh Kudurumalla
2023-12-07 10:38 ` Sunil Kumar Kori
2023-12-05 9:27 ` [PATCH v4 3/3] app/graph: implement port forward usecase Rakesh Kudurumalla
2023-12-07 11:07 ` Sunil Kumar Kori
2023-12-07 8:26 ` [EXT] [PATCH v4 1/3] node: support to add next node to ethdev Rx node Sunil Kumar Kori
2023-12-07 9:30 ` David Marchand
2023-12-15 9:15 ` [PATCH v5 " Rakesh Kudurumalla
2023-12-15 9:15 ` [PATCH v5 2/3] app/graph: add ethdev forward command Rakesh Kudurumalla
2023-12-18 10:44 ` Sunil Kumar Kori
2023-12-15 9:15 ` [PATCH v5 3/3] app/graph: implement port forward usecase Rakesh Kudurumalla
2023-12-18 10:57 ` Sunil Kumar Kori
2023-12-18 10:41 ` [EXT] [PATCH v5 1/3] node: support to add next node to ethdev Rx node Sunil Kumar Kori
2023-12-20 8:59 ` [PATCH v6 " Rakesh Kudurumalla
2023-12-20 8:59 ` [PATCH v6 2/3] app/graph: add ethdev forward command Rakesh Kudurumalla
2023-12-20 8:59 ` [PATCH v6 3/3] app/graph: implement port forward usecase Rakesh Kudurumalla
2023-12-20 9:44 ` [PATCH v7 1/3] node: support to add next node to ethdev Rx node Rakesh Kudurumalla
2023-12-20 9:44 ` [PATCH v7 2/3] app/graph: add ethdev forward command Rakesh Kudurumalla
2023-12-20 9:44 ` [PATCH v7 3/3] app/graph: implement port forward usecase Rakesh Kudurumalla
2024-01-01 8:37 ` [PATCH v8 1/3] node: support to add next node to ethdev Rx node Rakesh Kudurumalla
2024-01-01 8:37 ` [PATCH v8 2/3] app/graph: add ethdev forward command Rakesh Kudurumalla
2024-01-02 6:45 ` Sunil Kumar Kori
2024-01-01 8:37 ` [PATCH v8 3/3] app/graph: implement port forward usecase Rakesh Kudurumalla
2024-01-02 6:46 ` Sunil Kumar Kori
2024-01-02 7:28 ` [PATCH v9 1/3] node: support to add next node to ethdev Rx node Rakesh Kudurumalla
2024-01-02 7:28 ` [PATCH v9 2/3] app/graph: add ethdev forward command Rakesh Kudurumalla
2024-01-02 7:28 ` [PATCH v9 3/3] app/graph: implement port forward usecase Rakesh Kudurumalla
2024-01-02 7:30 ` [PATCH v10 1/3] node: support to add next node to ethdev Rx node Rakesh Kudurumalla
2024-01-02 7:30 ` [PATCH v10 2/3] app/graph: add ethdev forward command Rakesh Kudurumalla
2024-01-02 7:30 ` [PATCH v10 3/3] app/graph: implement port forward usecase Rakesh Kudurumalla
2024-02-18 22:22 ` Thomas Monjalon
2024-02-19 3:14 ` Jerin Jacob [this message]
2024-01-02 9:20 ` [EXT] [PATCH v10 1/3] node: support to add next node to ethdev Rx node Sunil Kumar Kori
2024-02-18 23:15 ` Thomas Monjalon
2024-02-18 23:17 ` 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=CALBAE1ORQg_ai0cSdnFSU-15doOvbOT++RePUF7YR6o3mGmRkQ@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=rkudurumalla@marvell.com \
--cc=skori@marvell.com \
--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).