All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: David Young <dave@youngcopy.com>
Cc: dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>,
	Aaron Conole <aconole@redhat.com>
Subject: Re: [PATCH v4 6/6] Section 6: Glossary
Date: Wed, 11 Sep 2024 08:55:51 -0700	[thread overview]
Message-ID: <20240911085551.03dd1a9e@hermes.local> (raw)
In-Reply-To: <20231123012633.2005-7-dave@youngcopy.com>

On Wed, 22 Nov 2023 20:26:27 -0500
David Young <dave@youngcopy.com> wrote:

> -Glossary Introduction Formatting: Refined the introduction's formatting for clarity.
> -Directive Implementation: Used .. glossary:: directive for structured term definitions.
> -Term Definitions and Linking: Expanded definitions for terms like BIOS,
> Bifurcated Driver, Clang-LLVM, etc., with reference tags and links to their respective
> content pages.
> Enhanced Navigation: Integrated hyperlinks for each term, directing to detailed information 
> on content pages.
> ---
>  doc/guides/getting_started_guide/glossary.rst | 78 +++++++++++++++++++
>  1 file changed, 78 insertions(+)
>  create mode 100644 doc/guides/getting_started_guide/glossary.rst
> 
> diff --git a/doc/guides/getting_started_guide/glossary.rst b/doc/guides/getting_started_guide/glossary.rst
> new file mode 100644
> index 0000000000..29e3f041ba
> --- /dev/null
> +++ b/doc/guides/getting_started_guide/glossary.rst
> @@ -0,0 +1,78 @@
> +..  SPDX-License-Identifier: BSD-3-Clause
> +    Copyright(c) 2010-2025 Intel Corporation.
> +
> +Glossary
> +========
> +
> +This glossary provides definitions for key terms and concepts used within DPDK. Understanding 
> +these terms will help in comprehending the functionality and architecture of DPDK.


Just for giggles asked ChatGpt to make a glossary

Creating a glossary for terms used in the DPDK (Data Plane Development Kit) documentation involves defining key concepts, components, and terminology relevant to DPDK. Here's a glossary to help you navigate the DPDK documentation:

A
Adapter: A hardware component that facilitates the communication between the CPU and network interface card (NIC).
B
Burst: A group of packets processed or transmitted in a single operation or cycle.
C
Core: A processing unit within a CPU that can execute tasks independently. In DPDK, cores are often used to handle packet processing.
Core Mask: A bitmask used to specify which CPU cores should be used by DPDK applications.
Configuration File: A file used to configure the DPDK environment, including options for devices and performance parameters.
D
DPDK: Data Plane Development Kit, a set of libraries and drivers for fast packet processing.
Driver: Software that allows DPDK to interact with hardware components like NICs.
Direct Memory Access (DMA): A method for hardware components to access system memory without involving the CPU, improving performance.
E
Ethernet: A common networking technology used for local area networks (LANs). DPDK often deals with Ethernet packets.
F
Flow: A sequence of packets with common characteristics, such as source and destination addresses, that can be processed together.
Frame: A packet of data transmitted over a network.
G
Gigabit Ethernet (GbE): A standard for Ethernet networks that supports data rates of 1 gigabit per second.
H
Hardware Abstraction Layer (HAL): An abstraction layer that hides the complexity of hardware interactions from higher-level software.
I
Interrupt: A signal sent to the CPU by hardware or software indicating an event that needs immediate attention.
IP (Internet Protocol): A protocol used for routing packets across network boundaries.
J
Jumbo Frame: Ethernet frames that are larger than the standard maximum transmission unit (MTU) size, used to improve network efficiency.
K
Kernel: The core part of an operating system that manages system resources and hardware communication.
L
Latency: The time delay between sending and receiving data, critical for performance in packet processing.
M
Memory Pool: A pool of pre-allocated memory blocks used for efficient allocation and deallocation of memory for packet processing.
N
NIC (Network Interface Card): A hardware component that connects a computer to a network.
NUMA (Non-Uniform Memory Access): A memory design where memory access time depends on the memory location relative to a processor, affecting performance in multi-core systems.
O
Offloading: The process of delegating certain tasks from the CPU to hardware components to improve performance.
P
Packet: A unit of data transmitted over a network.
Poll Mode Driver (PMD): A driver that uses busy polling to check for incoming packets, providing lower latency and higher performance compared to interrupt-driven drivers.
Pipeline: A series of processing stages through which packets pass.
Q
Queue: A buffer where packets are stored temporarily before being processed or transmitted.
R
RTE (Runtime Environment): The environment provided by DPDK to manage resources and execute applications.
Ring Buffer: A circular buffer used to manage data efficiently, often for inter-process communication.
S
Socket: A communication endpoint used in network programming. In DPDK, it refers to the hardware or memory allocation context associated with a CPU core.
Shared Memory: A memory space that can be accessed by multiple processes or threads, used in DPDK for inter-process communication.
T
Thread: A separate path of execution within a process, allowing concurrent operations.
U
Uplink: A connection from a device to a higher-level network, often used to refer to connections between switches or routers.
V
Virtualization: The creation of virtual instances of hardware or software resources, such as virtual NICs, to improve resource utilization.
W
Workload: The amount of processing or network traffic handled by DPDK applications.
X
X86 Architecture: A family of instruction set architectures used in most CPUs, supported by DPDK.
Y
Yield: The process of allowing other threads or processes to run, typically used in context with CPU resource management.
Z
Zero-Copy: A technique where data is transferred without being copied between buffers, reducing overhead and improving performance.
This glossary covers a broad range of terms relevant to DPDK, but you might encounter additional terms specific to certain features or components of the DPDK ecosystem. For detailed explanations and up-to-date information, always refer to the official DPDK documentation.

  parent reply	other threads:[~2024-09-11 15:55 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-03  4:01 [PATCH v3 0/7] docs: getting started guide consolidation David Young
2023-11-03  4:01 ` [PATCH v3 1/7] Section 1: Introduction David Young
2023-11-03 13:11   ` Bruce Richardson
2023-11-03  4:01 ` [PATCH v3 2/7] Section 2: Install and Build DPDK David Young
2023-11-03 13:55   ` Bruce Richardson
2023-11-03  4:01 ` [PATCH v3 3/7] Section 3: Setting up a System to Run DPDK Applications David Young
2023-11-03 14:17   ` Bruce Richardson
2023-11-03  4:01 ` [PATCH v3 4/7] Section 4: Running Applications David Young
2023-11-03 15:13   ` Bruce Richardson
2023-11-03  4:01 ` [PATCH v3 5/7] Section 5: Appendix David Young
2023-11-03 15:23   ` Bruce Richardson
2023-11-16  1:28     ` Dave Young
2023-11-17 13:04       ` Bruce Richardson
2023-11-03  4:01 ` [PATCH v3 6/7] Added link to Getting Started Guide in index.rst David Young
2023-11-03 13:32   ` Bruce Richardson
2023-11-03 14:22   ` Bruce Richardson
2023-11-08  1:47     ` Dave Young
2023-11-08  2:06       ` Dave Young
2023-11-03  4:01 ` [PATCH v3 7/7] Section 6: Glossary David Young
2023-11-03 15:26   ` Bruce Richardson
2023-11-23  1:26 ` [PATCH v4 0/6] docs: getting started guide consolidation David Young
2023-11-23  1:26   ` [PATCH v4 1/6] Section 1: Introduction David Young
2023-11-23  1:26   ` [PATCH v4 2/6] Section 2: Install and Build DPDK David Young
2023-11-23  1:26   ` [PATCH v4 3/6] Section 3: Setting up a System to Run DPDK Applications David Young
2023-11-23  1:26   ` [PATCH v4 4/6] Section 4: Running Applications David Young
2023-11-23  1:26   ` [PATCH v4 5/6] Section 5: Appendix David Young
2023-11-23  1:26   ` [PATCH v4 6/6] Section 6: Glossary David Young
2024-09-11 15:54     ` Stephen Hemminger
2024-09-11 15:55     ` Stephen Hemminger [this message]
2023-12-01 15:17   ` [PATCH v4 0/6] docs: getting started guide consolidation Thomas Monjalon
2024-10-04 16:29   ` Stephen Hemminger

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=20240911085551.03dd1a9e@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=aconole@redhat.com \
    --cc=bruce.richardson@intel.com \
    --cc=dave@youngcopy.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 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.