From: Aaron Wood <woody77@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Frits Riep <riep@riepnet.com>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Network behavior of Moca bridges
Date: Tue, 15 Apr 2014 23:30:58 +0200 [thread overview]
Message-ID: <CALQXh-OizJV4iVvmJMEdxDY_DEv_YFPs5MHwS8XK3SAoOsNPqw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6K6DAxbLCPYxG8AWZLjj8_08nhjyjRWTNdP-WjfcOPgQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1311 bytes --]
In about 2 months, I'll have my hands on some HomePlugAV devices that I can
do extensive testing with. My previous tests were showing very, very large
bufferbloat, when used on poor links (2000ms of buffering and growing over
a 1-2 minute rrul test that wasn't able to get over 10Mbps due to SF
Victorian wiring issues).
-Aaron
On Tue, Apr 15, 2014 at 11:05 PM, Dave Taht <dave.taht@gmail.com> wrote:
> I'd like to note that I've got several private reports of really bad,
> oft bufferbloated and (also underbuffered!) behavior on moca bridges,
> and if you are in a position to benchmark such, more public data on
> the problems would be nice.
>
> It generally looks like the same folk that designed homeplug products
> were involved in moca, with similar behaviors as described below with
> hardware flow control and the like, in addition to possible
> underbuffering and issues with shared media backoffs...
>
> http://caia.swin.edu.au/reports/130121A/CAIA-TR-130121A.pdf
>
> http://caia.swin.edu.au/reports/130417A/CAIA-TR-130417A.pdf
>
> But we lack hard public data on how the moca devices actually work or
> public testing.
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
[-- Attachment #2: Type: text/html, Size: 2049 bytes --]
next prev parent reply other threads:[~2014-04-15 21:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 21:05 Dave Taht
2014-04-15 21:30 ` Aaron Wood [this message]
2014-04-16 11:58 ` Frits Riep
2014-04-17 19:09 ` Chris Lawrence
2014-04-17 19:48 ` Dave Taht
2014-04-17 20:03 ` Dave Taht
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=CALQXh-OizJV4iVvmJMEdxDY_DEv_YFPs5MHwS8XK3SAoOsNPqw@mail.gmail.com \
--to=woody77@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=riep@riepnet.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