From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Dave Taht <dave.taht@gmail.com>
Cc: "aqm@ietf.org" <aqm@ietf.org>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [aqm] ping loss "considered harmful"
Date: Mon, 2 Mar 2015 05:05:18 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.02.1503020500340.20507@uplift.swm.pp.se> (raw)
In-Reply-To: <CAA93jw7KW=9PH002d3Via5ks6+mHScz5VDhpPVqLUGK2K=Mhew@mail.gmail.com>
On Sun, 1 Mar 2015, Dave Taht wrote:
> 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.
>
> How can we fix this user perception, short of re-prioritizing ping in
> sqm-scripts?
People will make all kinds of judgement calls based on things that are not
very relevant.
Some people think a traceroute with few hops in it to be better than one
with more hops in it. So a lot of providers use their MPLS networks and
make the intermediate nodes not show up in traceroute.
I don't know how many times I have experienced people have used PING and
opened trouble tickets when a core router had ICMP ping packet loss (even
though all core router platforms have rate limiters for ICMP).
When you say that you de-prioritize ping, do you mean only ECHO REQUEST
and ECHO REPLY, or do you mean all ICMP? Perhaps a solution would be to
assure 5% of the link bandwidth for ICMP?
--
Mikael Abrahamsson email: swmike@swm.pp.se
next prev parent reply other threads:[~2015-03-02 4:05 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-02 3:57 [Cerowrt-devel] " Dave Taht
2015-03-02 4:00 ` [Cerowrt-devel] [aqm] " Andrew Mcgregor
2015-03-02 4:05 ` Mikael Abrahamsson [this message]
2015-03-02 4:06 ` [Cerowrt-devel] " David Lang
2015-03-02 9:40 ` [Cerowrt-devel] [aqm] " Brian Trammell
2015-03-02 10:17 ` Mikael Abrahamsson
2015-03-02 10:54 ` [Cerowrt-devel] [Bloat] " Jonathan Morton
2015-03-02 12:44 ` dpreed
2015-03-02 14:45 ` Brian Trammell
2015-03-02 18:41 ` David Lang
2015-03-03 6:45 ` [Cerowrt-devel] " Valdis.Kletnieks
2015-03-04 8:14 ` Mikael Abrahamsson
2015-03-02 21:53 ` Joe Touch
2015-03-02 23:14 ` David Lang
2015-03-02 23:25 ` Joe Touch
2015-03-02 23:34 ` David Lang
2015-03-03 0:07 ` Andrew Mcgregor
2015-03-02 10:47 ` Dave Dolson
2015-03-02 10:49 ` Andrew Mcgregor
2015-03-02 18:36 ` David Lang
[not found] ` <md2fsa$o1s$1@ger.gmane.org>
2015-03-02 20:33 ` Dave Dolson
2015-03-02 20:39 ` David Lang
2015-03-02 20:38 ` Dave Taht
2015-03-04 8:12 ` Mikael Abrahamsson
2015-03-03 17:20 ` Fred Baker (fred)
2015-03-03 17:29 ` [Cerowrt-devel] [Bloat] " Wesley Eddy
2015-03-03 18:00 ` [Cerowrt-devel] [aqm] [Bloat] " Fred Baker (fred)
2015-03-04 5:24 ` Dave Taht
2015-03-05 18:56 ` Curtis Villamizar
2015-03-05 19:50 ` [Cerowrt-devel] [Bloat] [aqm] " Rich Brown
2015-03-04 17:34 ` [Cerowrt-devel] [aqm] [Bloat] " dpreed
2015-03-04 19:45 ` Mikael Abrahamsson
2015-03-05 20:38 ` [Cerowrt-devel] " Matt Taggart
2015-03-05 20:53 ` Dave Taht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.02.1503020500340.20507@uplift.swm.pp.se \
--to=swmike@swm.pp.se \
--cc=aqm@ietf.org \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox