From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/DTS Bug 1752] Add ASCII Art to DTS Docs
Date: Mon, 14 Jul 2025 14:49:41 +0000 [thread overview]
Message-ID: <bug-1752-3@https.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 4536 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1752
Bug ID: 1752
Summary: Add ASCII Art to DTS Docs
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: enhancement
Priority: Normal
Component: DTS
Assignee: dev@dpdk.org
Reporter: dmarx@iol.unh.edu
CC: juraj.linkes@pantheon.tech, probb@iol.unh.edu
Target Milestone: ---
Add ASCII art to illustrate concepts laid out in DTS documentation. For
example,
2 link topology:
+------------------------------+
+------------------------------+
| | |
|
| | --------------- |
|
| | |
|
| Tester (Traffic Generator) | | System Under Test
|
| | |
|
| | --------------- |
|
| | |
|
+------------------------------+
+------------------------------+
1 link topology:
+------------------------------+
+------------------------------+
| | |
|
| | --------------- |
|
| | |
|
| Tester (Traffic Generator) | | System Under Test
|
| | |
|
| | |
|
| | |
|
+------------------------------+
+------------------------------+
2 link topology on a single host:
-----------------------------------
| |
| ------------------------- |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
+--------------------------------------------------+
| |
| |
| |
| |
| Combined Tester & SUT system |
| |
| |
-
| |
| |
+--------------------------------------------------+
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 6466 bytes --]
reply other threads:[~2025-07-14 14:49 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-1752-3@https.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.org \
/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.