From: Aaron Wood <woody77@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Richard Smith <smithbone@gmail.com>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] bugs using the 1200ac as a target
Date: Wed, 27 Apr 2016 15:34:04 -0700 [thread overview]
Message-ID: <CALQXh-PDA38h=D=S6xD+=3RurEoekerrDw-q8snP+zhOuRe2mA@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7dDcWr_TxXmkAuw1Kc7S45tRcw8q26n0XBZWh5CUcAwQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1539 bytes --]
That's behavior I've seen multiple times in the past, but I never had a
good feel for what the cause was.
-Aaron
On Wed, Apr 27, 2016 at 3:08 PM, Dave Taht <dave.taht@gmail.com> wrote:
> run netserver on the router. It doesn't seem to matter what qdisc is
> on the router.
>
> hit it with the flent rrul_be or rrul tests. (or just multiple netperfs)
>
> You'll see one flow completely take over the router in this case and
> the others starve.
>
> On Wed, Apr 27, 2016 at 3:04 PM, Richard Smith <smithbone@gmail.com>
> wrote:
> > On 04/25/2016 11:56 PM, Dave Taht wrote:
> >>
> >> it has something deeply wrong in it at a gbit. In this test I'd failed
> >> over to a faster link at a gigE to show WTF it does - one flow totally
> >> wipes out the others.
> >>
> >>
> >>
> http://blog.cerowrt.org/flent/failing_over_faster/linksys_1200_majorly_headblocking.svg
> >
> >
> > What's your test conditions? I'll duplicate the test on my 1900acs and
> see
> > if it's there as well.
> >
> >
> > --
> > Richard A. Smith
> > _______________________________________________
> > Cerowrt-devel mailing list
> > Cerowrt-devel@lists.bufferbloat.net
> > https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
>
>
> --
> Dave Täht
> Let's go make home routers and wifi faster! With better software!
> http://blog.cerowrt.org
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
[-- Attachment #2: Type: text/html, Size: 2747 bytes --]
next prev parent reply other threads:[~2016-04-27 22:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 3:56 Dave Taht
2016-04-27 22:04 ` Richard Smith
2016-04-27 22:08 ` Dave Taht
2016-04-27 22:34 ` Aaron Wood [this message]
2016-05-02 17:03 ` Richard Smith
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-PDA38h=D=S6xD+=3RurEoekerrDw-q8snP+zhOuRe2mA@mail.gmail.com' \
--to=woody77@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=smithbone@gmail.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