From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: andinipersad361@gmail.com,
Stephen Hemminger <stephen@networkplumber.org>
Subject: [RFC] doc: restructure the introduction
Date: Tue, 10 Sep 2024 21:27:26 -0700 [thread overview]
Message-ID: <20240911042800.9203-1-stephen@networkplumber.org> (raw)
Add an about DPDK section (taken from web site), and a glossary.
Split the Programmer's Guide and Devices section.
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
Rough draft as starting point.
Need to also cleanup headers of the sub-sections
doc/guides/glossary/index.rst | 26 ++++++++++++++++++++++++++
doc/guides/index.rst | 35 ++++++++++++++++++++++++++++++-----
2 files changed, 56 insertions(+), 5 deletions(-)
create mode 100644 doc/guides/glossary/index.rst
diff --git a/doc/guides/glossary/index.rst b/doc/guides/glossary/index.rst
new file mode 100644
index 0000000000..5da74758b0
--- /dev/null
+++ b/doc/guides/glossary/index.rst
@@ -0,0 +1,26 @@
+.. SPDX-License-Identifier: BSD-3-Clause
+ Copyright 2024 The DPDK contributors
+
+Glossary of Terms
+==================
+
+EAL
+ Environment Abstraction Layer. Originally used to isolate differences between running
+ on bare metal versus running as a userspace process. Bare metal is no longer supported.
+ Now used to provide abstraction across operating system envrionments.
+
+Process
+ An operating system process consisting of one or more threads.
+
+Thread
+ The unit of execution in the operating system. A thread maybe bound to a specific physical
+ core on the CPU or migrate among core's via the operating system scheduler.
+
+Lcore
+ A logical core. In DPDK lcore's are usually bound to a isolated physical CPU core.
+
+Isolated core
+ A core is isolated if it is reserved by the operating system and not used for normal
+ (muggle) processes. The operating system scheduler will not migrate a thread onto an
+ isolated core; the only way a thread will run on an isolated core is by requesting
+ affinity to that core.
diff --git a/doc/guides/index.rst b/doc/guides/index.rst
index 244b99624c..ed3557f070 100644
--- a/doc/guides/index.rst
+++ b/doc/guides/index.rst
@@ -1,20 +1,48 @@
.. SPDX-License-Identifier: BSD-3-Clause
Copyright(c) 2010-2019 Intel Corporation.
-DPDK documentation
-==================
+############################################
+What is the Dataplane Development Kit (DPDK)
+############################################
+
+The Dataplane Development Kit (DPDK) is a set of libraries to accelerate packet processing
+workloads running on a wide variety of CPU architectures.
+
+Network performance, throughput, and latency are crucial for diverse applications, including wireless and wireline infrastructure, routers, load balancers, firewalls, video streaming, and VoIP. DPDK (Data Plane Development Kit), an open source project hosted by the Linux Foundation, provides a robust framework that boosts packet processing speeds on various CPU architectures like Intel x86, ARM, and PowerPC. This framework is key to rapidly developing high-speed data packet networking applications.
+
+By running DPDK, new users can significantly accelerate their network applications’ performance due to its efficient run-to-completion model and optimized libraries that ensure all necessary resources are allocated upfront.
.. toctree::
+ :caption: About DPDK
+ :maxdepth: 1
+
+ glossary/index
+ contributing/index
+ rel_notes/index
+ faq/index
+
+.. toctree::
+ :caption: Getting Started
:maxdepth: 1
linux_gsg/index
freebsd_gsg/index
windows_gsg/index
sample_app_ug/index
+
+.. toctree::
+ :caption: Programmers Guide
+ :maxdepth: 1
+
prog_guide/index
howto/index
tools/index
testpmd_app_ug/index
+
+.. toctree::
+ :caption: Device Drivers
+ :maxdepth: 1
+
nics/index
bbdevs/index
cryptodevs/index
@@ -28,6 +56,3 @@ DPDK documentation
rawdevs/index
mempool/index
platform/index
- contributing/index
- rel_notes/index
- faq/index
--
2.45.2
reply other threads:[~2024-09-11 4:28 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=20240911042800.9203-1-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--cc=andinipersad361@gmail.com \
--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 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).