Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Bloat] great interview on the scale conference wifi successes
Date: Thu, 12 Mar 2015 17:53:59 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.02.1503121751290.21504@nftneq.ynat.uz> (raw)
In-Reply-To: <CAA93jw5-b75sUmVHiqs6ftPM7dtn7d4-KJdq4+rg6fA+VQ0tUQ@mail.gmail.com>

On Thu, 12 Mar 2015, Dave Taht wrote:

> so the wifi and ethernet queues are fq_codeled in this past SCALE.
>
> One little understood fact about aggregated' wifi is that you CAN
> actually FQ the faster rate ethernet queue with the theoretically
> slower rate wifi queue, because a wifi aggregate is decoded at memory
> speeds, not wire or wireless speeds, and thus, can fill the BQL
> ethernet driver queue and have packets stuck at the qdisc layer, where
> they can be handled more smartly.
>
> That said, don't know if that ever happened at scale without data.
>
> The wifi outgoing interfaces on each AP on the other hand, could very
> well have had either the fq or the codel portions of the algorithm
> engage... they certainly do on my tests here.
>
> Although dlang did get quite a lot of data (which I have not yet seen,
> or have I had time for - does anyone here have time to analyze it? He
> got a ton of minstrel statistics in particular), but I am unsure if he
> collected any of the tc -s qdisc data from the wifi interfaces. (?)

no, I missed/forgot the request for that.

it's about 20G of data uncompressed, I'm running lzma on it now to see how small 
it will shrink.

> I also have to note that the ath9k driver has got so good now, that a
> ton of the benefit at scale probably came from that, and a great deal
> more, from dlang's excellent design for the network itself. It is sad,
> of course, that useful functionality like sta-to-sta transfers has to
> be disabled in such environments nowadays.
> I am really sorry I couldn't go.
>
> I am seeing 25% better forwarding rates on ethernet out of 3.18 vs
> 3.10 on the same wndr 3800 hardware, btw.

hmm, does this have a noticable effect on the HTB throttling performance?

David Lang

      reply	other threads:[~2015-03-13  0:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-10 18:26 [Cerowrt-devel] " Dave Taht
2015-03-10 20:44 ` [Cerowrt-devel] [Bloat] " David Lang
2015-03-10 21:12   ` Dave Taht
2015-03-10 21:34     ` David Lang
2015-03-12 15:31     ` Richard Smith
2015-03-12 16:13       ` dpreed
2015-03-12 23:58         ` David Lang
2015-03-13  0:08           ` Dave Taht
2015-03-13  0:53             ` David Lang [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=alpine.DEB.2.02.1503121751290.21504@nftneq.ynat.uz \
    --to=david@lang.hm \
    --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