From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id D7F333CB37; Wed, 4 Aug 2021 08:46:32 -0400 (EDT) Received: by uplift.swm.pp.se (Postfix, from userid 501) id 9E5ECB2; Wed, 4 Aug 2021 14:46:30 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1628081190; bh=2WP/D5/3jkmDAnOUzMzqYCFyFSzijLovaTb8AOAlHH8=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=N7LRD8H9tkTzmMyyEIMZIuNaT3OJcp2I9Wg7XMcEkrFVJ2R6t0olkIHlZej3qVVMo fRaa17xkEfLZaZJTV0rSVwa5o0nM3vxi3nspZ4o1CXaYkF8GClAlzgLSajBNx1CESj jp6EvVwIda/686QjnBnq6uI3mmVFI/mcsUtyuSYU= Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 9B1E8B0; Wed, 4 Aug 2021 14:46:30 +0200 (CEST) Date: Wed, 4 Aug 2021 14:46:30 +0200 (CEST) From: Mikael Abrahamsson To: Jonathan Morton cc: dickroy@alum.mit.edu, starlink@lists.bufferbloat.net, Simon Barber , bloat In-Reply-To: Message-ID: References: <058681B8-89EB-42ED-8E82-4048BA3C9504@cable.comcast.com> <649DC4B024D74B8BA6926ABFCD52DC79@SRA6> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) Organization: People's Front Against WWW MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Subject: Re: [Starlink] [Bloat] Of interest: Comcast AQM Paper 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: Wed, 04 Aug 2021 12:46:33 -0000 On Wed, 4 Aug 2021, Jonathan Morton wrote: > Linux-based CPE devices have AQM functionality integrated into the Wifi > stack. The AQM itself operates at layer 3, but the Linux Wifi stack > implementation uses information from layers 2 and 4 to improve > scheduling decisions, eg. airtime-fairness and flow-isolation (FQ). This > works best on soft-MAC Wifi hardware, such as ath9k/10k and MT76, where > this information is most readily available to software. In principle it > could also be implemented in the MAC, but I don't know of any vendor > that's done that yet. Does this work also with flowoffload enabled, or is that not accelerated on for instance MT76? I'm surprised since MT76 can barely do 100 meg/s of large packets using only CPU? -- Mikael Abrahamsson email: swmike@swm.pp.se