General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Rick Jones <rick.jones2@hp.com>
To: Rich Brown <richb.hanover@gmail.com>,
	 Jonathan Morton <chromatix99@gmail.com>
Cc: dpreed@reed.com, "Wes Felter" <wmf@felter.org>,
	"Joel Wirāmu Pauling" <joel@aenertia.net>,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [Cerowrt-devel] Fixing bufferbloat: How about an open letter to the web benchmarkers?
Date: Fri, 12 Sep 2014 08:24:58 -0700	[thread overview]
Message-ID: <5413104A.4070104@hp.com> (raw)
In-Reply-To: <AFED1384-C717-4D26-BA9E-1C32401A074C@gmail.com>

On 09/11/2014 06:48 PM, Rich Brown wrote:
> Jonathan,
>
>> Could we make use of the existing test servers (running netperf) for that demonstration?  How hard is the protocol to fake in Javascript?
>
> Not having coded a stitch of this, I *think* it would require the following:
>
> - Web page on netperf-xxx.bufferbloat.net that served out the javascript (required to get around cross-domain protections within the browser)
>
> - Javascript function to connect back to that host on port 12865 and fake out the netserver with TCP_STREAM or TCP_MAERTS request
>
> - Javascript that's efficient enough to source/swallow full-rate data stream
>
> - Cloning the code from https://github.com/apenwarr/blip to make fake pings from TCP requests
>
> Anyone know more than I do about this?

Not about the javascript stuff, but your high level description of the 
netperf side sounds plausible.  There are a few control messages netperf 
will exchange with netserver that if you want to leverage a remote 
netserver will need to be included.  You can run a netperf command with 
a higher debug level to see them.

rick jones

  reply	other threads:[~2014-09-12 15:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-11 16:03 [Bloat] " Dave Taht
2014-09-11 16:35 ` Pedro Tumusok
2014-09-11 18:19 ` [Bloat] [Cerowrt-devel] " Maciej Soltysiak
2014-09-12  0:13 ` [Bloat] " Rich Brown
2014-09-12  0:35   ` [Bloat] [Cerowrt-devel] " dpreed
2014-09-12  0:42     ` Jonathan Morton
2014-09-12  1:24       ` dpreed
     [not found]         ` <CAKiAkGTwgoJvNJ_C+RUx5rLJDENJhu4p7nQO_TbOA_mNWMQv2Q@mail.gmail.com>
2014-09-12  2:04           ` Jonathan Morton
2014-09-12  1:48       ` Rich Brown
2014-09-12 15:24         ` Rick Jones [this message]
2014-09-13  0:19           ` David P. Reed
2014-09-12  7:17   ` [Bloat] " Jesper Dangaard Brouer
2014-09-12 12:16     ` Rich Brown
2014-09-12 12:55       ` Jesper Dangaard Brouer
2014-09-12  0:31 ` [Bloat] [Cerowrt-devel] " dpreed
2014-09-12  9:44 ` Toke Høiland-Jørgensen

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=5413104A.4070104@hp.com \
    --to=rick.jones2@hp.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --cc=dpreed@reed.com \
    --cc=joel@aenertia.net \
    --cc=richb.hanover@gmail.com \
    --cc=wmf@felter.org \
    /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