From: David Lang <david@lang.hm>
To: Pete Heist <pete@heistp.net>
Cc: Dave Taht <dave@taht.net>, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] one benefit of turning off shaping + fq_codel
Date: Tue, 4 Dec 2018 16:25:02 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.02.1812041623530.19784@nftneq.ynat.uz> (raw)
In-Reply-To: <FA85339A-094E-46EC-8B38-BFDB9EEEB994@heistp.net>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 397 bytes --]
On Sat, 24 Nov 2018, Pete Heist wrote:
>> But outbound is not the problem for us from a heat generation standpoint…
>
> Actually, why is inbound shaping that much harder on the CPU than outbound?
Because you don't control the flow directly, you are trying to control the
remote sender indirectly by delaying acks and dropping packets to trick the
sending stack into slowing down.
David Lang
next prev parent reply other threads:[~2018-12-05 1:25 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-13 16:54 Dave Taht
2018-11-14 17:09 ` Mikael Abrahamsson
2018-11-15 0:56 ` David Lang
2018-11-15 3:44 ` Dave Taht
2018-11-23 11:47 ` Pete Heist
2018-11-23 16:26 ` Dave Taht
2018-11-23 16:43 ` Jonathan Morton
2018-11-23 16:48 ` Dave Taht
2018-11-23 17:16 ` Luca Muscariello
2018-11-23 17:27 ` Dave Taht
2018-11-23 17:32 ` Luca Muscariello
2018-11-25 21:14 ` Toke Høiland-Jørgensen
2018-11-26 12:52 ` Pete Heist
2018-11-26 12:54 ` Dave Taht
2018-11-26 13:30 ` Toke Høiland-Jørgensen
2018-11-26 13:26 ` Toke Høiland-Jørgensen
2018-11-24 11:49 ` Pete Heist
2018-12-05 0:25 ` David Lang [this message]
2018-11-27 18:14 ` Holland, Jake
2018-11-27 18:31 ` Stephen Hemminger
2018-11-27 19:09 ` Dave Taht
2018-11-27 22:07 ` Pete Heist
2018-11-27 22:33 ` Jonathan Morton
2018-11-27 22:36 ` Jonathan Morton
2018-11-28 7:23 ` [Bloat] hardware diversions Dave Taht
2018-11-27 19:11 ` [Bloat] one benefit of turning off shaping + fq_codel Holland, Jake
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.02.1812041623530.19784@nftneq.ynat.uz \
--to=david@lang.hm \
--cc=bloat@lists.bufferbloat.net \
--cc=dave@taht.net \
--cc=pete@heistp.net \
/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