From: "Lương Việt Hoàng" <tcm4095@gmail.com>
To: stephen@networkplumber.org
Cc: netdev@vger.kernel.org, "Lương Việt Hoàng" <tcm4095@gmail.com>
Subject: [PATCH iproute2] tc-cake: document 'ingress'
Date: Sun, 11 Aug 2024 21:26:17 +0700 [thread overview]
Message-ID: <20240811142756.12225-2-tcm4095@gmail.com> (raw)
Linux kernel commit 7298de9cd7255a783ba ("sch_cake: Add ingress mode") added
an ingress mode for CAKE, which can be enabled with the 'ingress' parameter.
Document the changes in CAKE's behavior when ingress mode is enabled.
Signed-off-by: Lương Việt Hoàng <tcm4095@gmail.com>
---
man/man8/tc-cake.8 | 15 +++++++++++++++
1 file changed, 15 insertions(+)
diff --git a/man/man8/tc-cake.8 b/man/man8/tc-cake.8
index ced9ac78..6d77d7d2 100644
--- a/man/man8/tc-cake.8
+++ b/man/man8/tc-cake.8
@@ -541,6 +541,21 @@ This can be used to set policies in a firewall script that will override CAKE's
built-in tin selection.
.SH OTHER PARAMETERS
+.B ingress
+.br
+ Indicates that CAKE is running in ingress mode (i.e. running on the downlink
+of a connection). This changes the shaper to also count dropped packets as data
+transferred, as these will have already traversed the link before CAKE can
+choose what to do with them.
+
+ In addition, the AQM will be tuned to always keep at least two packets
+queued per flow. The reason for this is that retransmits are more expensive in
+ingress mode, since dropped packets have to traverse the link again; thus,
+keeping a minimum number of packets queued will improve throughput in cases
+where the number of active flows are so large that they saturate the link even
+at their minimum window size.
+
+.PP
.B memlimit
LIMIT
.br
--
2.45.2
next reply other threads:[~2024-08-11 14:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-11 14:26 Lương Việt Hoàng [this message]
2024-08-11 16:35 ` [PATCH iproute2] tc-cake: document 'ingress' Stephen Hemminger
-- strict thread matches above, loose matches on Subject: below --
2024-08-12 23:41 a
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=20240811142756.12225-2-tcm4095@gmail.com \
--to=tcm4095@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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.