From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gatekeeper1-relay.space.net (gatekeeper1-relay.space.net [IPv6:2001:608:3:85::38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id C6FD73CB37 for ; Fri, 7 Jun 2024 03:51:26 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=space.net; i=@space.net; q=dns/txt; s=esa; t=1717746687; x=1749282687; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=nm4BiI/Ll3wiozMaqMIQtI4s7AO19tbNk99Pbc2XJ98=; b=XR4DIYY790PcN7O0Hlp8y6oSj13Yr3hz+PfFCbuAmXeAKZ9upxK//hHi j+VgwMKLtJ9rPj2ILN+EzBwio7zDzEdntZGhD91PeFDcxkK8RnMxxHXkx c74LiokGsbQd1+uggvEtRpYb+MBuIH5hqGmMw55EUwr6acYH3mDdTPO5f +gJR8JMtAdOOhY35mXvv3XKFxCtzOGYqhgwQIRJFVn41DMz56Fnl0AmWC LwYu+M/8CjDQX8xdNaxMGHMy8wrr4js1P1/sE302S9gu69cr/tLMeEa/s nJSudPQciKUEcFg3GR5AbLlJyh8ZWIvS1xeJpmu+NXtTCKWqkS01Ne9Es w==; X-CSE-ConnectionGUID: ShoCfLhUQMyr9pLxQNyKoQ== X-CSE-MsgGUID: OD+IH3LBT4ebaT4c2YKpEA== X-SpaceNet-SBRS: None Received: from mobil.space.net ([195.30.115.67]) by gatekeeper1-relay.space.net with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 07 Jun 2024 09:51:25 +0200 Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id D5C3543059 for ; Fri, 7 Jun 2024 09:51:24 +0200 (CEST) X-SpaceNet-Relay: true Received: from moebius4.space.net (moebius4.space.net [IPv6:2001:608:2:2::251]) by mobil.space.net (Postfix) with ESMTP id C175843029; Fri, 7 Jun 2024 09:51:24 +0200 (CEST) Received: by moebius4.space.net (Postfix, from userid 1007) id B9EE531C38; Fri, 7 Jun 2024 09:51:24 +0200 (CEST) Date: Fri, 7 Jun 2024 09:51:24 +0200 From: Gert Doering To: Sebastian Moeller Cc: Dave Taht , Dave Taht via Starlink , Stuart Cheshire , Colin_Higbie Message-ID: References: <3FF32F52-4A93-496B-85FF-00020FA4A48B@gmx.de> <08F6942E-CC08-4956-B92E-CBEC091D86E4@ieee.org> <2F510BD5-2D7E-4A6A-A3DE-C529D14F6FBC@apple.com> <0D6DC1A5-4934-43A3-9F0A-A637E8FD1A76@gmx.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0D6DC1A5-4934-43A3-9F0A-A637E8FD1A76@gmx.de> Subject: Re: [Starlink] The "reasons" that bufferbloat isn't a problem X-BeenThere: starlink@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Starlink has bufferbloat. Bad." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jun 2024 07:51:27 -0000 Hi, On Fri, Jun 07, 2024 at 07:36:36AM +0200, Sebastian Moeller via Starlink wrote: > it might show that big iron silicon is just inferior to general purpose CPUs Well, different criteria for "inferior", I'd say. A general purpose CPU won't be able to feed something with 24x 100Gbit - and a switch network processor won't be good for running a database... For queueing/shaping, the network chips have become surprisingly good - not sure about libreqos & friends, but "doing proper shaping to sub- linerate to avoid policing drops in a carrier network further downstream" was something switches just couldn't do, and recent gear (Jericho 2+) does this quite well. With proper burst size configured, no bufferbloat there either :) Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard, Ingo Lalla, Karin Schuler, Sebastian Cler Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279