From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.lang.hm (h-66-167-227-145.lsan.ca.dynamic.globalcapacity.com [66.167.227.145]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 741A73B2A4 for ; Tue, 4 Dec 2018 20:25:14 -0500 (EST) Received: from asgard.lang.hm (syslog [10.0.0.100]) by mail.lang.hm (Postfix) with ESMTP id 0E86F44970; Tue, 4 Dec 2018 17:25:11 -0800 (PST) Date: Tue, 4 Dec 2018 16:25:02 -0800 (PST) From: David Lang X-X-Sender: dlang@asgard.lang.hm To: Pete Heist cc: Dave Taht , bloat In-Reply-To: Message-ID: References: <6C1479A8-43E8-4F89-BCEA-1D28CA3E8589@heistp.net> <87r2fbzrng.fsf@taht.net> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="680960-445966784-1543969502=:19784" Subject: Re: [Bloat] one benefit of turning off shaping + fq_codel X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Dec 2018 01:25:14 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --680960-445966784-1543969502=:19784 Content-Type: TEXT/PLAIN; charset=utf-8; format=flowed Content-Transfer-Encoding: 8BIT 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 --680960-445966784-1543969502=:19784--