From: Aaron Wood <woody77@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Bloat] sqm-scripts on WRT1900AC
Date: Sat, 23 May 2015 23:51:08 -0700 [thread overview]
Message-ID: <CALQXh-Pa9cYYQPsThbgODxsnPKr9BPyr_b1ikzuvQCYmHZgSOg@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw5Ab1=eghXtd4Qjp9brHFe1yxkFSvjY+muLYXHjL4M-CA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1222 bytes --]
On Sat, May 23, 2015 at 11:44 PM, Dave Taht <dave.taht@gmail.com> wrote:
>
> And it has a fan. Hate fans. Amusingly (I guess), I had this same
> chipset to fiddle with in the "mirabox" and it ran waaaay too hot.
>
I haven't hit the fan, yet....
> It is not clear why you are getting an inaccurate rate out of it, either.
>
I feel like the rate has never been really accurate, or perhaps it's just
that we're jut not properly accounting in our measurement tools (netperf),
for the ACK bandwidth. But my current "limited" rate is set higher than
anything I've ever measured, and it's clearly still working. Part of my
next rounds of testing are to keep pushing that up until it's clear that
I've tripped over the "real" rate.
It is a leading candidate, but I would prefer to find a hardware
> partner that cared about our issues enough to work with us, rather
> than ignore us as netgear did.
>
I fear that's going to be a continual issue while we ask for things that
most people don't understand that they want/need. But I think that we'll
have an easier time if we're talking with a chipset vendor (like Marvell)
vs an OEM (like Netgear), given the relative distance each has from the
kernel drivers...
-Aaron
[-- Attachment #2: Type: text/html, Size: 2013 bytes --]
prev parent reply other threads:[~2015-05-24 6:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-24 5:17 [Cerowrt-devel] " Aaron Wood
2015-05-24 6:19 ` Aaron Wood
2015-05-25 23:55 ` [Cerowrt-devel] [Bloat] " David Lang
2015-05-29 8:34 ` Pedro Tumusok
2015-05-29 9:09 ` David Lang
2015-05-29 10:04 ` Pedro Tumusok
2015-05-29 20:26 ` David Lang
2015-06-01 8:47 ` Pedro Tumusok
2015-05-24 6:44 ` Dave Taht
2015-05-24 6:51 ` Aaron Wood [this message]
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-Pa9cYYQPsThbgODxsnPKr9BPyr_b1ikzuvQCYmHZgSOg@mail.gmail.com \
--to=woody77@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@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