From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Jim Geo <dim.geo@gmail.com>, cake@lists.bufferbloat.net
Subject: Re: [Cake] cake ingress switch
Date: Sat, 26 Feb 2022 21:10:06 +0100 [thread overview]
Message-ID: <87ilt1v17l.fsf@toke.dk> (raw)
In-Reply-To: <CAD9MmSd=Wxu5qQAdFwrNEf4guHt7QMC5zkcd9_kCFAZsuXigQQ@mail.gmail.com>
Jim Geo <dim.geo@gmail.com> writes:
> Hello,
>
> Was it the function of ingress argument in cake?
> Checking online man pages, I couldn't find an explanation.
> Does it make sense to use it on an ifb device? (sending ingress
> traffic through it)
Yes, that's exactly what it's meant for. The option changes cake's
accounting so that packets that are dropped are accounted as part of the
effective bandwidth of the link (since on ingress, even if they're
dropped they have already traversed the bottleneck link). This should
help keep the bottleneck under tighter control...
-Toke
prev parent reply other threads:[~2022-02-26 20:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 22:13 Jim Geo
2022-02-26 20:10 ` Toke Høiland-Jørgensen [this message]
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
List information: https://lists.bufferbloat.net/postorius/lists/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ilt1v17l.fsf@toke.dk \
--to=toke@toke.dk \
--cc=cake@lists.bufferbloat.net \
--cc=dim.geo@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