From: Jesper Louis Andersen <jesper.louis.andersen@gmail.com>
To: Richard Scheffenegger <rscheff@gmx.at>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Background Bufferbloat Detector
Date: Thu, 17 Feb 2011 00:34:39 +0100 [thread overview]
Message-ID: <AANLkTimtgd7r8V3m7n9QfFG9q1aLn5dqrzsNCN=a0LhX@mail.gmail.com> (raw)
In-Reply-To: <6F4E15F3B5314030A7C34DCC49395D8B@srichardlxp2>
On Wed, Feb 16, 2011 at 20:03, Richard Scheffenegger <rscheff@gmx.at> wrote:
>
> Perhaps Bittorrent Clients can be used to export the one-way delay, as
> measured by the µTP protocol, to build an complementary background
> bufferbloat detector [..]
>
> And, hosting legal content on one's own Bittorrent Client should provide
> ample opportunity to get decent measurements, without the need to negotiate
> with someone else about taking readings off some debug-log from an NTP
> server....
>
The only "slight" problem is that not all clients support µTP. You are
limited to hacking either KTorrent 4.0+ (C++) or Vuze (Java). There
are C clients in progression however (Transmission, libtorrent). My
"own" client (in Erlang) has been putting off the implementation,
mostly because I'd rather see TCP fixed :) But perhaps this could be a
good opportunity to just hack up that protocol :)
BitTorrent also has the advantage that it often connects to hosts from
all over the world, so if there is any indication in the data, it
should definitely be able to see a trend.
--
J.
next prev parent reply other threads:[~2011-02-16 23:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 17:46 Sean Conner
2011-02-16 18:48 ` Dave Täht
2011-02-16 19:03 ` Richard Scheffenegger
2011-02-16 23:34 ` Jesper Louis Andersen [this message]
2011-02-16 23:39 ` Juliusz Chroboczek
2011-02-16 23:51 ` Dave Täht
2011-02-18 20:08 ` Richard Scheffenegger
2011-02-18 20:17 ` Dave Täht
2011-02-18 21:27 ` Juliusz Chroboczek
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='AANLkTimtgd7r8V3m7n9QfFG9q1aLn5dqrzsNCN=a0LhX@mail.gmail.com' \
--to=jesper.louis.andersen@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=rscheff@gmx.at \
/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