General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: Jesper Dangaard Brouer <brouer@redhat.com>
Cc: Jonathan Morton <chromatix99@gmail.com>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] ADSL, ATM drivers, bloat, education & confusion
Date: Thu, 11 Jun 2015 13:57:47 +0200	[thread overview]
Message-ID: <A0DDFA8E-7FA4-416F-9C83-2DF59ED82403@gmx.de> (raw)
In-Reply-To: <20150611132434.564c382c@redhat.com>

Hi Jesper.

On June 11, 2015 1:24:34 PM GMT+02:00, Jesper Dangaard Brouer <brouer@redhat.com> wrote:
>
>On Sat, 6 Jun 2015 16:30:51 +0200 Sebastian Moeller <moeller0@gmx.de>
>wrote:
>
>> On Jun 6, 2015, at 15:53 , Jonathan Morton <chromatix99@gmail.com>
>wrote:
>> 
>> > You will need to set the overhead calculation correctly, probably
>> > using "pppoa-vcmux" or similar, depending on precisely what
>> > encapsulation your ISP uses. If you're not confident about that,
>> > specify "conservative" to begin with.
>> 
>> 	I can be of help to measure the overhead empirically, if you
>> are willing to dedicate a few hours on an otherwise quiescent link to
>> gather some ICMP data, just let me know.
>
>It would be really cool if someone developed a (simple) tool that could
>probe (a quiescent) ADSL/ATM link, and report the encapsulation
>overhead (AFAIKR there are 12 different encap combi-types on ADSL).


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...


Best Regards
        Sebastian

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

  reply	other threads:[~2015-06-11 11:58 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 [this message]
2015-06-11 14:14         ` Tristan Seligmann
2015-06-11 21:03           ` Sebastian Moeller
2015-06-12  6:45             ` Jesper Dangaard Brouer
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=A0DDFA8E-7FA4-416F-9C83-2DF59ED82403@gmx.de \
    --to=moeller0@gmx.de \
    --cc=bloat@lists.bufferbloat.net \
    --cc=brouer@redhat.com \
    --cc=chromatix99@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