From: Dave Taht <dave.taht@gmail.com>
To: Felix Fietkau <nbd@openwrt.org>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] another contender for WNDR replacement
Date: Sun, 25 Jan 2015 11:16:02 -0800 [thread overview]
Message-ID: <CAA93jw5F5LFSxBAGhV4v+gOk8tLtM88PUofVyk_67rBaT1NNvg@mail.gmail.com> (raw)
In-Reply-To: <54C4CEE3.2040909@openwrt.org>
On Sun, Jan 25, 2015 at 3:09 AM, Felix Fietkau <nbd@openwrt.org> wrote:
> Here's another candidate:
> http://us.dlink.com/products/connect/wireless-ac1200-dual-band-gigabit-cloud-router-dir-860l/
>
> CPU: MT7621 (dual-core MIPS, 880 MHz, 4 virtual CPUs)
> The device has preliminary OpenWrt support already. In my tests, handles
> ~820 Mbit/s NAT without any special acceleration features (with fq_codel,
> no shaping). Haven't done any tests with shaping yet.
One of the many things on my todo list is to roll an RFC in the hope some vendor
can meet it. High on that list would be the ability to do inbound
traffic shaping at
up to about 300Mbits.
> Wifi (MT7612E) is still buggy with my mt76 driver, but I'll fix that in
> March when I get back from vacation.
Ah, this is the new chip with the driver support for actually implementing per
tid (station) queues? Is this the master repo for that or is it mainlined?
https://github.com/openwrt/mt76/commits/master
Guess we have to get around to implementing a codel with a weighted
per-active-station average for the target, and start layering the other
stuff in on top...
>
> - Felix
--
Dave Täht
thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks
next prev parent reply other threads:[~2015-01-25 19:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-19 13:46 Sebastian Moeller
2015-01-19 16:37 ` Dave Taht
2015-01-19 23:44 ` Sebastian Moeller
2015-01-25 11:09 ` Felix Fietkau
2015-01-25 19:16 ` Dave Taht [this message]
2015-01-25 19:28 ` Felix Fietkau
2015-02-18 9:28 ` Sebastian Moeller
2015-02-18 9:30 ` Dave Taht
2015-02-18 9:38 ` 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=CAA93jw5F5LFSxBAGhV4v+gOk8tLtM88PUofVyk_67rBaT1NNvg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=nbd@openwrt.org \
/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