From: <luca.muscariello@orange.com>
To: Jonathan Morton <chromatix99@gmail.com>, David Lang <david@lang.hm>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] RE : Detecting bufferbloat from outside a node
Date: Mon, 4 May 2015 22:02:37 +0000 [thread overview]
Message-ID: <4462_1430776959_5547EC7F_4462_1827_1_qa64b6fyc2xtwd2cfxqtgm4f.1430776543085@email.android.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1870 bytes --]
offered traffic as Neil is using it is, makes sense for an aggregate of flows that varies over time.
low load would mean that for a some relatively long period of time all flows have finished while none have started yet. In the standard 5min average that means that you capture a fraction of data from the few that happened to be active in that window.
but when the system is non empty whatever the number of flows is the link can be fully utilized if that link is the bottleneck.
-------- Message d'origine --------
De : Jonathan Morton
Date :2015/05/04 17:39 (GMT-04:00)
À : David Lang
Cc : bloat
Objet : Re: [Bloat] Detecting bufferbloat from outside a node
Or you are defining various terms in a way that makes no sense to us. Given that you're obviously working with core rather than edge networks, that is entirely possible.
- Jonathan Morton
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
[-- Attachment #2: Type: text/html, Size: 2311 bytes --]
reply other threads:[~2015-05-04 22:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4462_1430776959_5547EC7F_4462_1827_1_qa64b6fyc2xtwd2cfxqtgm4f.1430776543085@email.android.com \
--to=luca.muscariello@orange.com \
--cc=bloat@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=david@lang.hm \
/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