netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: "Lương Việt Hoàng" <tcm4095@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2] tc-cake: document 'ingress'
Date: Sun, 11 Aug 2024 09:35:45 -0700	[thread overview]
Message-ID: <20240811093546.52c88499@hermes.local> (raw)
In-Reply-To: <20240811142756.12225-2-tcm4095@gmail.com>

On Sun, 11 Aug 2024 21:26:17 +0700
Lương Việt Hoàng <tcm4095@gmail.com> wrote:

>  .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

Hadn't looked at the man page for CAKE in detail before, but it appears
to be trying to pre-format lots of stuff rather than using man format (nroff)
like other man pages.

For example: indenting the start of the paragraph in nroff source is odd
and unnecessary.

  reply	other threads:[~2024-08-11 16:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-11 14:26 [PATCH iproute2] tc-cake: document 'ingress' Lương Việt Hoàng
2024-08-11 16:35 ` Stephen Hemminger [this message]
  -- 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=20240811093546.52c88499@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=netdev@vger.kernel.org \
    --cc=tcm4095@gmail.com \
    /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).