From: Jesper Dangaard Brouer <brouer@redhat.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: Jonathan Morton <chromatix99@gmail.com>,
Van Jacobson <vanj@google.com>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] ADSL, ATM drivers, bloat, education & confusion
Date: Fri, 12 Jun 2015 08:45:51 +0200 [thread overview]
Message-ID: <20150612084551.3fdafac4@redhat.com> (raw)
In-Reply-To: <93F98697-31A7-4AFB-978A-C32F398C220A@gmx.de>
On Thu, 11 Jun 2015 23:03:18 +0200 Sebastian Moeller <moeller0@gmx.de> wrote:
> On Jun 11, 2015, at 16:14 , Tristan Seligmann <mithrandi@mithrandi.net> wrote:
>
> > On Thu, 11 Jun 2015 at 13:58 Sebastian Moeller <moeller0@gmx.de> wrote:
> >
> > I sort of did, but it takes a relative long time to gather data
> > (typically around 3 hours) plus 15 minutes for the analysis. I am
> > happy to share this with interested parties...
> >
> > I would definitely be interested in this for myself.
>
> Sure I will send it your way this weekend (need to do a tiny
> bit of clean-up and actually want to put it into git and possibly
> git-hub). It essentially is a shell script that runs ping and a
> matlab/octave script that does attempts the ATM detection, so far it
> worked well, but it is by no way automatic (yet)….
Please also send it my way. (But I don't have time to look at it before
*after* netfilter workshop[1])
One hint when detecting this, use the *minimum* observed latency/ping
for a given packet size, as jitter/other-traffic can only increase the
latency, but cannot lower it. (This is an idea that I picked up from
Van Jacobsson).
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Sr. Network Kernel Developer at Red Hat
Author of http://www.iptv-analyzer.org
LinkedIn: http://www.linkedin.com/in/brouer
[1] http://workshop.netfilter.org/2015/
next prev parent reply other threads:[~2015-06-12 6:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-06 13:38 Kevin Darbyshire-Bryant
2015-06-06 13:53 ` Jonathan Morton
2015-06-06 14:30 ` Sebastian Moeller
2015-06-11 11:24 ` Jesper Dangaard Brouer
2015-06-11 11:57 ` Sebastian Moeller
2015-06-11 14:14 ` Tristan Seligmann
2015-06-11 21:03 ` Sebastian Moeller
2015-06-12 6:45 ` Jesper Dangaard Brouer [this message]
2015-06-06 15:04 ` Sebastian Moeller
2015-06-06 14:29 ` Sebastian Moeller
2015-06-06 15:46 ` Kevin Darbyshire-Bryant
2015-06-06 15:50 ` Dave Taht
2015-06-06 18:14 ` Sebastian Moeller
2015-06-07 13:29 ` Kevin Darbyshire-Bryant
2015-06-11 11:16 ` Jesper Dangaard Brouer
2015-06-11 11:51 ` Sebastian Moeller
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=20150612084551.3fdafac4@redhat.com \
--to=brouer@redhat.com \
--cc=bloat@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=moeller0@gmx.de \
--cc=vanj@google.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