From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-out02.uio.no (mail-out02.uio.no [IPv6:2001:700:100:8210::71]) (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 4461D3B29E for ; Tue, 6 Oct 2020 07:25:41 -0400 (EDT) Received: from mail-mx11.uio.no ([129.240.10.83]) by mail-out02.uio.no with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93.0.4) (envelope-from ) id 1kPl6A-00058R-U5 for make-wifi-fast@lists.bufferbloat.net; Tue, 06 Oct 2020 13:25:38 +0200 Received: from boomerang.ifi.uio.no ([129.240.68.135]) by mail-mx11.uio.no with esmtpsa (TLS1.2:ECDHE-RSA-AES256-GCM-SHA384:256) user michawe (Exim 4.93.0.4) (envelope-from ) id 1kPl6A-000CMD-Gl for make-wifi-fast@lists.bufferbloat.net; Tue, 06 Oct 2020 13:25:38 +0200 From: Michael Welzl Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Message-Id: Date: Tue, 6 Oct 2020 13:25:36 +0200 To: make-wifi-fast@lists.bufferbloat.net X-Mailer: Apple Mail (2.3445.9.1) X-UiO-SPF-Received: Received-SPF: neutral (mail-mx11.uio.no: 129.240.68.135 is neither permitted nor denied by domain of ifi.uio.no) client-ip=129.240.68.135; envelope-from=michawe@ifi.uio.no; helo=boomerang.ifi.uio.no; X-UiO-Spam-info: not spam, SpamAssassin (score=-5.0, required=5.0, autolearn=disabled, AWL=0.034, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO, uiouri=NO) X-UiO-Scanned: 8170E8892207ADD6264937D858314F3F358BFB4B Subject: [Make-wifi-fast] Where is the bloat in WiFi? X-BeenThere: make-wifi-fast@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Oct 2020 11:25:41 -0000 Hi all, A simple question to y'all who spent so much time on Cake and things ... = in a household using WiFi, which buffer is usually bloated? Where does = the latency really come from? Is it: 1. the access point's downlink queue, feeding into the WiFi network, 2. the modem's downlink queue, feeding into the access point, 3. the modem's uplink queue, 4. the access point's uplink queue towards the modem (hm, that seems = silly, surely the AP-modem connection is fast... so perhaps, instead: = the queue in the host, as it wants to send data towards the access = point) or is it a combination of these? I guess that, with openwrt, Cake is operating on the queue that's = feeding the wifi network, as the modem's queue is out of its control... = so: is this where the bottleneck usually is? Just wondering about your views and experiences. Thanks in advance! Cheers, Michael -- PS: my personal guess: 1 and 3 above are the most common. But that's = *pure* guesswork!