From: Dave Taht <dave.taht@gmail.com>
To: Frits Riep <riep@riepnet.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] Network behavior of Moca bridges
Date: Tue, 15 Apr 2014 14:05:36 -0700 [thread overview]
Message-ID: <CAA93jw6K6DAxbLCPYxG8AWZLjj8_08nhjyjRWTNdP-WjfcOPgQ@mail.gmail.com> (raw)
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.
next reply other threads:[~2014-04-15 21:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 21:05 Dave Taht [this message]
2014-04-15 21:30 ` Aaron Wood
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=CAA93jw6K6DAxbLCPYxG8AWZLjj8_08nhjyjRWTNdP-WjfcOPgQ@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--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