Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Alan Jenkins <alan.christopher.jenkins@gmail.com>,
	cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] SQM and PPPoE, more questions than answers...
Date: Thu, 19 Mar 2015 07:01:42 -0700	[thread overview]
Message-ID: <CAA93jw6jDGefAzsoGUhYwHUuVzU9yJMAaf1iDj4rYwZGRg0Ctg@mail.gmail.com> (raw)
In-Reply-To: <87619x84w4.fsf@toke.dk>

On Thu, Mar 19, 2015 at 6:59 AM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
> Alan Jenkins <alan.christopher.jenkins@gmail.com> writes:
>
>> I also notice that my test with eth1 (disabling classification) is the
>> only one where UDP ping (including UDP EF) is visible for any time at
>> all. (ok, pppoe-wan shows UDP BK, and it very clearly gets higher
>> latency as I would expect).
>
> FYI the svn version of netperf has a feature to restart the UDP
> measurement flows after a timeout. If you build that (don't forget the
> --enable-demo switch to ./configure) and stick it in your $PATH,
> netperf-wrapper should pick it up automatically and use the option. This
> might get you better results on the UDP flows...

I note that time of first loss is a valuable statistic in itself, and
I would like
to see it called out more on the measurement flows on the graph.

> -Toke
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel



-- 
Dave Täht
Let's make wifi fast, less jittery and reliable again!

https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb

      reply	other threads:[~2015-03-19 14:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-11 23:12 Sebastian Moeller
2014-10-15  0:03 ` Sebastian Moeller
2014-10-15 12:02   ` Török Edwin
2014-10-15 13:39     ` Sebastian Moeller
2014-10-15 17:28       ` Dave Taht
2014-10-15 19:55         ` Sebastian Moeller
2015-03-18 22:14   ` Alan Jenkins
2015-03-19  2:43     ` David Lang
2015-03-19  3:11       ` Dave Taht
2015-03-19  8:37       ` Sebastian Moeller
2015-03-19  8:29     ` Sebastian Moeller
2015-03-19  9:42       ` Alan Jenkins
2015-03-19  9:58         ` Sebastian Moeller
2015-03-19 13:49       ` Alan Jenkins
2015-03-19 13:59         ` Toke Høiland-Jørgensen
2015-03-19 14:01           ` Dave Taht [this message]

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=CAA93jw6jDGefAzsoGUhYwHUuVzU9yJMAaf1iDj4rYwZGRg0Ctg@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=alan.christopher.jenkins@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=toke@toke.dk \
    /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