From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-1.mimecast.com (us-smtp-2.mimecast.com [205.139.110.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id B46443B2A4 for ; Thu, 24 Oct 2019 08:14:14 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1571919254; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=MoY/6TAJSbS7YlPyOTVp/94SJGxeK4WyiG3Hoa3SOhw=; b=ErVnufKL8OYyigzX7V/ul+Y/JB+K5dDq+s8mgc20vqkcTfbSm81WYaOJt56hWRMn9blBn5 X2m/+ST6NEtAaFAzLl1JmYfmzhRJFM7SKMOhpHt2FnHXIbPFeipnBtLsyyNJx7isylRZBG e9eeYKQQiK8ZNi17TDnR8SMLfFhdfcs= Received: from mail-lf1-f70.google.com (mail-lf1-f70.google.com [209.85.167.70]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-264-YzkCF9bjOa-UlhP8Ue7xaw-1; Thu, 24 Oct 2019 08:14:12 -0400 Received: by mail-lf1-f70.google.com with SMTP id q7so553835lfd.4 for ; Thu, 24 Oct 2019 05:14:12 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:in-reply-to:references:date :message-id:mime-version; bh=qE5VVkM76kRJLiy815g4Rsf1awC8I57CfvFSOi7Y2vw=; b=TXUphghGn1ztETnGaU19cFCPWW5DbpNIlI0g3efgyLkUWWWVHJMlJ+esfBs9r+zaE7 gkNo0ttuJWWgG1KqAoHm4WPOkbyTjy0ef1n/thbMb+WCRbIIx4lUTjhiGUq5wVhla604 n6RLPxkKMrnHk02G9z7sjF/7fBnE/Rls7VFriJ5vtx3W1xR8WNmUqzdQtMvWZyxGpUz/ 8k2YG/fAxcHu1xvSgcZ90bSb36+MbIjn/1FKQpPFGMsdu8z7Y9Ya+VmZiK5g4f9Bryna IZmugb0t1SP0QBGUOtInN1z1qJ8PLosbjiumuPM/NltflG0z8sTPiwgco4KbErBm76Lx +V0A== X-Gm-Message-State: APjAAAWsIz1jFB1FZkFO+zr+dhf4gPHzRYUQZMNAJc23biJFDnBpuP3T eFNTOrWe54McpWMK8jt85QrnPZLix+djqj0HRXHyYXHtXmUT+karYAOSzLkFBOSCTZk1Y5EVpvq v2lRoaSvZQOTlHd7+qK7RVw0= X-Received: by 2002:a19:ca13:: with SMTP id a19mr2988753lfg.133.1571919250921; Thu, 24 Oct 2019 05:14:10 -0700 (PDT) X-Google-Smtp-Source: APXvYqy1RA4cvTLqhDvRntErwh5sUvcqTMcB+wrHEZw18KGzzA4JcyOpIZ9y1v4L/xi4VAntfM28pg== X-Received: by 2002:a19:ca13:: with SMTP id a19mr2988737lfg.133.1571919250721; Thu, 24 Oct 2019 05:14:10 -0700 (PDT) Received: from alrua-x1.borgediget.toke.dk ([2a00:7660:6da:443::2]) by smtp.gmail.com with ESMTPSA id m11sm5673993lfp.69.2019.10.24.05.14.09 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 24 Oct 2019 05:14:09 -0700 (PDT) Received: by alrua-x1.borgediget.toke.dk (Postfix, from userid 1000) id 1EDFE1804B1; Thu, 24 Oct 2019 14:14:09 +0200 (CEST) From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= To: erik.taraldsen@telenor.com, bloat@lists.bufferbloat.net In-Reply-To: <1571917896021.11761@telenor.com> References: <0876C235-C6D3-42B0-9D93-114DB75D4204@gmail.com> <1571917896021.11761@telenor.com> X-Clacks-Overhead: GNU Terry Pratchett Date: Thu, 24 Oct 2019 14:14:09 +0200 Message-ID: <87k18ul4ry.fsf@toke.dk> MIME-Version: 1.0 X-MC-Unique: YzkCF9bjOa-UlhP8Ue7xaw-1 X-Mimecast-Spam-Score: 0 Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable Subject: Re: [Bloat] Bufferbloat on 4G Connexion 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: Thu, 24 Oct 2019 12:14:14 -0000 writes: >> The key thing in both BQL and AQL is that instead of treating all packet= s the >> same, you account for how long it will take to transmit them. >> >> In Wifi, your transmission rate can vary by a factor of 1000x (1Mb to ov= er 1Gb >> per second), so just counting bytes as BQL does is no longer good enough= . >> >> how much does the actual over-the-air transmission rate vary in 4G? I'd = bet that >> it varies less than wifi does because wifi must retain compatibility wit= h the >> earliest equipment while 4G no longer supports 2G protocols. > > So in a scenario with a fixed (wall mounted outdoor unit) LTE device > BQL could work quite well as the radio will not fluctuate too much. > > But for a mobil "pocket router" being carried around an AQL approach > would be needed? Having setup such an outdoor-mounted unit, I'd say that it's probably a bit too optimistic to think that it doesn't fluctuate much. Cell scheduling parameters (including activity from other stations), as well as weather, can lead to quite significant fluctuations even in a physically static setup. So ideally, you'd want to be able to react to changes in either case. The firmware should certainly have enough information to do that, but if you can't get that changed, it may be possible to do something BQL-like (either AQL, or simply a more dynamic variant of BQL) on the host. -Toke