Re: [aqm] ping loss "considered harmful"
Andrew Mcgregor <andrewmcgr@google.com> Mon, 02 March 2015 04:00 UTC
Return-Path: <andrewmcgr@google.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C9891A002F for <aqm@ietfa.amsl.com>; Sun, 1 Mar 2015 20:00:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level:
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3aKY-8n3oQ0h for <aqm@ietfa.amsl.com>; Sun, 1 Mar 2015 20:00:41 -0800 (PST)
Received: from mail-qa0-x236.google.com (mail-qa0-x236.google.com [IPv6:2607:f8b0:400d:c00::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E5E81A000E for <aqm@ietf.org>; Sun, 1 Mar 2015 20:00:41 -0800 (PST)
Received: by mail-qa0-f54.google.com with SMTP id x12so21102092qac.13 for <aqm@ietf.org>; Sun, 01 Mar 2015 20:00:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=qjP4S3HlCoNev526H1QuQT9gCAkHY3GNu/gyUYdLghM=; b=A4JHqQNn/8z7YTq54xDWegqV090N2xMx7nS309Gw7/Yu8/Nav1fNfcMjNoVhtGfKqv kwecluUiNlb1h3lknG10Yd9AK/dNJMw6ZkrfM+ValWGhNHlyuHMsOx7OJfBf6f9QOfVa RGBrMrKDYC+kvL8dG8fRpO2GHCZSv+h29geXjKy5I90R4C6RUC8pILvD4LQ1okYJ1n0b YC5gipgCg4o2f553fmYjkIpsVZ2OIShiBiD83C+gy58azXaai5+i5L5OZNQnUbVAEf+N 8tAUo/+odEH2/49BIWFoKJfvCKN1dct36MVBQ7QMynhmVCBXB3Gx2IgApLMFu79LwbgB 65Tg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=qjP4S3HlCoNev526H1QuQT9gCAkHY3GNu/gyUYdLghM=; b=TFO7wQkqudM9Caci8BHtvcYiMYUgbfnIxSM9E/v3Spts+R2ahsg3YSsoSKJWIU9wQo ea/n2jGf64zlY7FnpuXKQHFZc5+V8S5Rrqd2fG4JBNoJqnNEzlXemDciQFv75JyK9EBu 1pMxOFM5geDD3NaYE9WSb6cgmUqfc8OUHwAeFAG8obUzGcN4sxbnkdcpNQJ3kdVs4sl8 2651UPy9A0abBFXtnJhQko9IYs9eHw6PdlMewwCmfjOPBRLfQyyPk+bpJUiXjQ3sgwpu qfDBOC/l0pFuXfCItJSMQPdcl3h//n0JKswno2i3eGPpwVeRX+fPAbWLSB4w1HvaIEia Ybrg==
X-Gm-Message-State: ALoCoQnvqPy49CPmsTuU2z5S+EyQiJvl4EzU9a9jYiuW+IvnOPNhFPnVNhcG7zCZi+/59XGmar5t
MIME-Version: 1.0
X-Received: by 10.140.51.107 with SMTP id t98mr45504248qga.63.1425268840451; Sun, 01 Mar 2015 20:00:40 -0800 (PST)
Received: by 10.96.68.74 with HTTP; Sun, 1 Mar 2015 20:00:40 -0800 (PST)
In-Reply-To: <CAA93jw7KW=9PH002d3Via5ks6+mHScz5VDhpPVqLUGK2K=Mhew@mail.gmail.com>
References: <CAA93jw7KW=9PH002d3Via5ks6+mHScz5VDhpPVqLUGK2K=Mhew@mail.gmail.com>
Date: Mon, 02 Mar 2015 15:00:40 +1100
Message-ID: <CAPRuP3kbDUq6MGbx5DaJxwt0+vcZwdfoNLirV4tr+-9gV-HRoQ@mail.gmail.com>
From: Andrew Mcgregor <andrewmcgr@google.com>
To: Dave Taht <dave.taht@gmail.com>
Content-Type: multipart/alternative; boundary="001a1135244ef1ffc6051046420b"
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/NwgFwrdO7pAeL2d395lQUEO07lg>
Cc: "aqm@ietf.org" <aqm@ietf.org>, "cerowrt-devel@lists.bufferbloat.net" <cerowrt-devel@lists.bufferbloat.net>, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [aqm] ping loss "considered harmful"
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion list for active queue management and flow isolation." <aqm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aqm>, <mailto:aqm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Mar 2015 04:00:43 -0000
Hash all pings into one fq_codel bucket reserved for the purpose, so if we're getting DoSed we drop them, otherwise if they stay thin they get prioritised? On 2 March 2015 at 14:57, Dave Taht <dave.taht@gmail.com> wrote: > On this thread over here, an otherwise pretty clueful user chose > openwrt's qos-scripts over the sqm-scripts, because sqm-scripts had > *higher ping loss*. > > > http://forums.dlink.com/index.php?topic=61634.msg251125#msg251125 > > (I note that both fq_codel enabled QoS systems outperformed > streamboost by a lot, which I am happy about) > > wow. It never registered to me that users might make a value judgement > based on the amount of ping loss, and in looking back in time, I can > think of multiple people that have said things based on their > perception that losing pings was bad, and that sqm-scripts was "worse > than something else because of it." > > sqm-scripts explicitly *deprioritizes* ping. In particular, this > reduces the impact of ping floods from ipv6 to your entire /64, or to > your whole ipv4, fairly well. And I had made the point that > prioritizing ping was a bad idea here (including some dripping sarcasm > later in the piece). > > http://www.bufferbloat.net/projects/cerowrt/wiki/Wondershaper_Must_Die > > but wow, it never occurred to me - in all these years - that ping was > the next core metric on simple tests. I can be really dumb. > > I use netperf-wrapper and tend to ignore most of the ping data, but > certainly on some benchmarks we have published ping doesn't look as > good as the other stuff, *because it is deprioritized below all the > other traffic*. Not strictly rate limited - as some systems do by > default, including openwrt, which is impossible to get right - just > deprioritized.... > > How can we fix this user perception, short of re-prioritizing ping in > sqm-scripts? > > -- > Dave Täht > Let's make wifi fast, less jittery and reliable again! > > https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb > > _______________________________________________ > aqm mailing list > aqm@ietf.org > https://www.ietf.org/mailman/listinfo/aqm > -- Andrew McGregor | SRE | andrewmcgr@google.com | +61 4 1071 2221
- [aqm] ping loss "considered harmful" Dave Taht
- Re: [aqm] ping loss "considered harmful" Andrew Mcgregor
- Re: [aqm] ping loss "considered harmful" Mikael Abrahamsson
- Re: [aqm] [Cerowrt-devel] ping loss "considered h… David Lang
- Re: [aqm] ping loss "considered harmful" Brian Trammell
- Re: [aqm] ping loss "considered harmful" Mikael Abrahamsson
- Re: [aqm] ping loss "considered harmful" Dave Dolson
- Re: [aqm] ping loss "considered harmful" Andrew Mcgregor
- Re: [aqm] [Cerowrt-devel] [Bloat] ping loss "cons… dpreed
- Re: [aqm] [Bloat] ping loss "considered harmful" Jonathan Morton
- Re: [aqm] [Bloat] ping loss "considered harmful" Brian Trammell
- Re: [aqm] [Cerowrt-devel] ping loss "considered h… David Lang
- Re: [aqm] ping loss "considered harmful" Wes Felter
- Re: [aqm] ping loss "considered harmful" Dave Dolson
- Re: [aqm] ping loss "considered harmful" Dave Taht
- Re: [aqm] ping loss "considered harmful" David Lang
- Re: [aqm] ping loss "considered harmful" Joe Touch
- Re: [aqm] ping loss "considered harmful" David Lang
- Re: [aqm] ping loss "considered harmful" Joe Touch
- Re: [aqm] ping loss "considered harmful" David Lang
- Re: [aqm] ping loss "considered harmful" Andrew Mcgregor
- Re: [aqm] ping loss "considered harmful" Wes Felter
- Re: [aqm] [Cerowrt-devel] ping loss "considered h… Valdis.Kletnieks
- Re: [aqm] ping loss "considered harmful" Fred Baker (fred)
- Re: [aqm] [Bloat] ping loss "considered harmful" Wesley Eddy
- Re: [aqm] [Bloat] ping loss "considered harmful" Fred Baker (fred)
- Re: [aqm] [Bloat] ping loss "considered harmful" Dave Taht
- Re: [aqm] ping loss "considered harmful" Mikael Abrahamsson
- Re: [aqm] [Cerowrt-devel] ping loss "considered h… Mikael Abrahamsson
- Re: [aqm] [Cerowrt-devel] [Bloat] ping loss "cons… dpreed
- Re: [aqm] [Cerowrt-devel] [Bloat] ping loss "cons… Mikael Abrahamsson
- Re: [aqm] [Bloat] ping loss "considered harmful" Curtis Villamizar
- Re: [aqm] [Cerowrt-devel] ping loss "considered h… Dave Taht
- Re: [aqm] [Bloat] ping loss "considered harmful" Rich Brown
- Re: [aqm] [Cerowrt-devel] ping loss "considered h… Matt Taggart