From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf0-x236.google.com (mail-lf0-x236.google.com [IPv6:2a00:1450:4010:c07::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id DAC4D3B2A0 for ; Thu, 2 Jun 2016 10:22:16 -0400 (EDT) Received: by mail-lf0-x236.google.com with SMTP id b73so35046190lfb.3 for ; Thu, 02 Jun 2016 07:22:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=cf3liUypaknbNuKoReUfOvW4UGPiQo8y8uSraCmMess=; b=PxOx37yDVpKQuhnxrf9XlGMUW2KUIOfo/zl9/zK+Y46Vd0TGZZhnIy7UR0HYFr37ZL iyMKprxyNqYxoTbddezGf4MZ9Vw+QqS2UX/YW/T12xPBCra4cdfwg23wTDwwLqVN6Vvq nTj5TK/yyejuoq2h/IRbguNETM7Jlp/vvu9JZ2Psu0kLNnZPsg7YwutX4DDglVjYQn5h lFHAtRteJRFV6zyZPeaMTG6HtMT3U2SC79cvzdRVWyk6juKo7iUbRTyY0TZwlQzqWwAO ZlhWqhxUEWXa8beXUrnEEypzP3JpdLROKSM+VbDOmUdCWlpqDM+xRIZ6BfREzdLx9/rZ B44g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=cf3liUypaknbNuKoReUfOvW4UGPiQo8y8uSraCmMess=; b=aswd5FI9r5bOC1OCg1RKPEBPItUH7SUG/u8SD4FDBQSqH0pAN5G+ihZ+RD4gljpTUo qsCt7bfz7ZMjXPTr+s0tDxU5/1IEaJ2wTFya7H3A/TLtQgu9ioiFwfrTwsY3rrxkv54h vmoWzEHJOlz/cZaUD9icira9L33mbhpXuBqyQUMdGJfZNqSCqP7SQ7W8k8BS8SncjcvR zBtazS90PUQ/Pq5htEdh8Lj0DlqUmaRziWh2jyLmMjs1tGsFgChQusJOuNx+I0C33rP8 jWtaJFtCauaUX8dqTiSch4cisOMZrjx/vaJM9N/tho0MoTTumb2amAwOkhIRN8AM3GGR 3Tdw== X-Gm-Message-State: ALyK8tJ1Phx4KnWt6cLmvGOMYqQ2WAmWF0/vs+75PZMXjkamV/rn4IBsSdldnEi89jz9VQ== X-Received: by 10.46.33.77 with SMTP id h74mr3930159ljh.50.1464877335164; Thu, 02 Jun 2016 07:22:15 -0700 (PDT) Received: from [192.168.100.11] (37-33-56-85.bb.dnainternet.fi. [37.33.56.85]) by smtp.gmail.com with ESMTPSA id h88sm3948122ljh.33.2016.06.02.07.22.13 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 02 Jun 2016 07:22:14 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) From: Jonathan Morton In-Reply-To: <574FFE52.1040501@darbyshire-bryant.me.uk> Date: Thu, 2 Jun 2016 17:22:03 +0300 Cc: cake@lists.bufferbloat.net Content-Transfer-Encoding: quoted-printable Message-Id: <2A84540D-AA30-4BD0-AF9A-5510EA00B7E8@gmail.com> References: <574FFE52.1040501@darbyshire-bryant.me.uk> To: Kevin Darbyshire-Bryant X-Mailer: Apple Mail (2.3124) Subject: Re: [Cake] cake/tc - removal of atm/ptm/ethernet specific overhead keywords X-BeenThere: cake@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Cake - FQ_codel the next generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2016 14:22:17 -0000 > On 2 Jun, 2016, at 12:37, Kevin Darbyshire-Bryant = wrote: >=20 > I'd be sort of interested to know if anyone is actually using those = keywords: ipoa-vcmux, ipoa-llcsnap, bridged-vcmux, bridged-llcsnap, = ppoa-vcmux, pppoa-llc, pppoe-vcmux, pppoe-llcsnap, pppoe-ptm, = bridged-ptm, via-ethernet, ether-phy, ether-all, ether-fcs, ether-vlan. >=20 > How many actually knew they even existed? Since they are poorly documented, probably not many. But I=E2=80=99d = rather improve the documentation than delete them. In principle, the existence and naming of these keywords is a potential = clue to the uninitiated user of the overhead feature=E2=80=99s purpose. = The concept of protocol overhead affecting shader function is not an = obvious one outside of networking specialists; making users look up a = number in a cryptic table will simply result in nobody doing it at all. Having shortcut keywords for this purpose in tc also helps to avoid the = trap of other UI layers doing their own (incomplete or inaccurate) = research on the correct compensation to apply. Currently LuCI is = extremely clumsy at handling SQM configuration, and the general quality = of vendor firmware doesn=E2=80=99t give me confidence. I=E2=80=99ve just pushed an update which makes all the keywords = incremental, rather than some of them being absolute. Existing correct = examples of how to use these keywords remain correct. It would be nice if LuCI could infer information about the likely = overheads from the rest of the configuration, and apply (or suggest & = default) the correct keywords in sqm-scripts. That would make the = feature much more widely used. - Jonathan Morton