From: Felix Fietkau <nbd@openwrt.org>
To: Dave Taht <dave.taht@gmail.com>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
Lorenzo Colitti <lorenzo@google.com>,
Jesper Dangaard Brouer <jbrouer@redhat.com>,
Andrew McGregor <andrewmcgr@gmail.com>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] some notes on the archer c7v2's suitability for make-wifi-fast
Date: Fri, 27 Mar 2015 21:06:56 +0100 [thread overview]
Message-ID: <5515B860.4090005@openwrt.org> (raw)
In-Reply-To: <CAA93jw5yfJd4miWWwqm1DoquVRsStV145B0XbzF+_PkA0dzC+A@mail.gmail.com>
On 2015-03-27 03:10, Dave Taht wrote:
> B) The bad news: I didn't get around to testing wifi at all. I ran
> into an interesting problem, where testing it with full nat enabled,
> with no sqm-scripts, would peak at about 400 mbits on the rrul test,
> and:
>
> 0) If hostapd was running it would run a lot - cutting performance by
> about 50Mbits on the test runs. I think I posted the strace here
> already.
Might be fixed in current trunk.
> While reducing queue size when running out of cpu is a pleasing
> result, it also points to possible tuning options for napi, maybe
> adding xmit_more support in (or removing it entirely), in order to
> fully service all interrupts in one direction or another, and also
> compile options specific to the mips74k which has a long pipeline in
> particular, and so far as I know the archer has no issues (as the
> wndr3800 had) with unaligned access so we can turn off various hacks
> on that front.
A while back, I tested xmit_more, and it didn't seem to be making any
visible difference on the router that I tested it on (MT7621).
- Felix
prev parent reply other threads:[~2015-03-27 20:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 2:10 Dave Taht
2015-03-27 2:25 ` [Cerowrt-devel] [Bloat] " Rich Brown
2015-03-27 2:30 ` Dave Taht
2015-03-27 2:30 ` Jonathan Morton
2015-03-27 5:05 ` Jonathan Morton
2015-03-27 20:06 ` Felix Fietkau [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=5515B860.4090005@openwrt.org \
--to=nbd@openwrt.org \
--cc=andrewmcgr@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=jbrouer@redhat.com \
--cc=lorenzo@google.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