public inbox for dev@dpdk.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>,
	Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Subject: [PATCH 5/5] doc: correct typos in traffic management guide
Date: Fri, 16 Jan 2026 13:29:36 -0800	[thread overview]
Message-ID: <20260116213100.110419-6-stephen@networkplumber.org> (raw)
In-Reply-To: <20260116213100.110419-1-stephen@networkplumber.org>

Two documentation issues corrected:
- Remove errant asterisk from "Head Drop*"
- Remove duplicate phrase in WRED algorithm description

Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
 doc/guides/prog_guide/ethdev/traffic_management.rst | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/doc/guides/prog_guide/ethdev/traffic_management.rst b/doc/guides/prog_guide/ethdev/traffic_management.rst
index c356791a45..086eb9d3af 100644
--- a/doc/guides/prog_guide/ethdev/traffic_management.rst
+++ b/doc/guides/prog_guide/ethdev/traffic_management.rst
@@ -109,15 +109,14 @@ They are made available for every leaf node in the hierarchy, subject to
 the specific implementation supporting them.
 On request of writing a new packet into the current queue while the queue is
 full, the Tail Drop algorithm drops the new packet while leaving the queue
-unmodified, as opposed to the Head Drop* algorithm, which drops the packet
+unmodified, as opposed to the Head Drop algorithm, which drops the packet
 at the head of the queue (the oldest packet waiting in the queue) and admits
 the new packet at the tail of the queue.
 
 The Random Early Detection (RED) algorithm works by proactively dropping more
 and more input packets as the queue occupancy builds up. When the queue is full
 or almost full, RED effectively works as Tail Drop. The Weighted RED (WRED)
-algorithm uses a separate set of RED thresholds for each packet color and uses
-separate set of RED thresholds for each packet color.
+algorithm uses a separate set of RED thresholds for each packet color.
 
 Each hierarchy leaf node with WRED enabled as its congestion management mode
 has zero or one private WRED context (only one leaf node using it) and/or zero,
-- 
2.51.0


  parent reply	other threads:[~2026-01-16 21:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-16 21:29 [PATCH 0/5] doc: ethdev documentation grammar and typo corrections Stephen Hemminger
2026-01-16 21:29 ` [PATCH 1/5] doc: correct grammar and punctuation errors in ethdev guide Stephen Hemminger
2026-01-16 21:29 ` [PATCH 2/5] doc: correct grammar in rte_flow guide Stephen Hemminger
2026-01-16 21:29 ` [PATCH 3/5] doc: correct grammar in QoS framework guide Stephen Hemminger
2026-01-16 21:29 ` [PATCH 4/5] doc: correct typos in switch representation guide Stephen Hemminger
2026-01-16 21:29 ` Stephen Hemminger [this message]
2026-01-28 19:45 ` [PATCH v2 0/8] doc: ethdev documentation grammar and typo corrections Stephen Hemminger
2026-01-28 19:46   ` [PATCH v2 1/8] doc: correct grammar and punctuation errors in ethdev guide Stephen Hemminger
2026-01-28 19:46   ` [PATCH v2 2/8] doc: correct grammar in flow guide Stephen Hemminger
2026-01-28 19:46   ` [PATCH v2 3/8] doc: correct grammar in QoS framework guide Stephen Hemminger
2026-01-28 19:46   ` [PATCH v2 4/8] doc: correct typos in switch representation guide Stephen Hemminger
2026-01-28 19:46   ` [PATCH v2 5/8] doc: correct typos in traffic management guide Stephen Hemminger
2026-01-28 19:46   ` [PATCH v2 6/8] doc: correct grammar and improve clarity in ethdev guide Stephen Hemminger
2026-03-25 11:41     ` Thomas Monjalon
2026-01-28 19:46   ` [PATCH v2 7/8] doc: correct alphabetical ordering in ethdev toctree Stephen Hemminger
2026-03-25 11:45     ` Thomas Monjalon
2026-01-28 19:46   ` [PATCH v2 8/8] doc: correct grammar and improve clarity in MTR guide Stephen Hemminger
2026-02-05 21:29   ` [PATCH v2 0/8] doc: ethdev documentation grammar and typo corrections 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=20260116213100.110419-6-stephen@networkplumber.org \
    --to=stephen@networkplumber.org \
    --cc=cristian.dumitrescu@intel.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