From: Jonathan Morton <chromatix99@gmail.com>
To: "Eggert, Lars" <lars@netapp.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Packet loss in FCC press release
Date: Fri, 27 Feb 2015 17:47:17 +0200 [thread overview]
Message-ID: <CAJq5cE2U8v=fpwdQQuTfdtZqQH7y=m5MfaQbd=MN+Sfqb6oFWA@mail.gmail.com> (raw)
In-Reply-To: <435DDB48-33B9-400A-ACE3-CD29C50CF6E3@netapp.com>
[-- Attachment #1: Type: text/plain, Size: 492 bytes --]
It's not ideal, but I'm not quite as worried about that as you might be.
There are several potential causes of packet loss in a network, and
increasing buffer sizes is only likely to have a minor and temporary effect
on one of them.
Meanwhile, increased deployment of ECN would permit adding AQM as a means
to decrease packet loss.
Random packet loss due to poor quality lines, and also due to dumb policers
and overloaded core routers, is probably what's intended here.
- Jonathan Morton
[-- Attachment #2: Type: text/html, Size: 580 bytes --]
next prev parent reply other threads:[~2015-02-27 15:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 10:49 Eggert, Lars
2015-02-27 15:47 ` Jonathan Morton [this message]
2015-02-27 16:35 ` Dave Taht
2015-02-27 19:47 ` Matt Mathis
2015-02-27 19:08 ` Rick Jones
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJq5cE2U8v=fpwdQQuTfdtZqQH7y=m5MfaQbd=MN+Sfqb6oFWA@mail.gmail.com' \
--to=chromatix99@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=lars@netapp.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