Lets make wifi fast again!
 help / color / mirror / Atom feed
From: Adrian Chadd <adrian@freebsd.org>
To: Henning Rogge <hrogge@gmail.com>
Cc: Wayne Workman <wayne.workman2012@gmail.com>,
	make-wifi-fast@lists.bufferbloat.net,
	 bufferbloat-fcc-discuss
	<bufferbloat-fcc-discuss@lists.redbarn.org>,
	 "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] [bufferbloat-fcc-discuss] arstechnica confirms tp-link router lockdown
Date: Sat, 12 Mar 2016 12:18:14 -0800	[thread overview]
Message-ID: <CAJ-Vmo=_zKnmN=yxDuTrKMPR_2gk+d1kzT0bsZYewTSMXCkcCg@mail.gmail.com> (raw)
In-Reply-To: <CAGnRvuouiRSKas8Fhzvn7xCzz5ON0=dgeeXiA_UuztRJ=gg9Yw@mail.gmail.com>

On 12 March 2016 at 11:14, Henning Rogge <hrogge@gmail.com> wrote:
> On Sat, Mar 12, 2016 at 3:32 PM, Wayne Workman
> <wayne.workman2012@gmail.com> wrote:
>> I understand that Broadcom was paid to develop the Pi, a totally free board.
>>
>> And they already make wireless chipsets.
>
> The question is how easy would it be to build a modern 802.11ac
> halfmac chip... the amount of work these chips do (especially with 3*3
> or 4*4 MIMO) is not trivial.

It's not that scary - most of the latency sensitive things are:

* channel change - eg background scans
* calibration related things - but most slow calibration could be done
via firmware commands, like the intel chips do!
* transmit a-mpdu / retransmit
* transmit rate control adaptation
* receiving / block-ack things - which is mostly done in hardware anyway
* likely some power save transition-y things too

If you're doing STA mode, then you have more things to do - eg bgscans
with active traffic, TDLS, P2P, etc.
If you're doing hostap mode or heck, even mostly-dumb ibss mode -
where there's no requirement for off-channel traffic - the firmware is
mostly just a transmit/receive engine and some power save stuff.

And honestly - know how many cycles a modern CPU has? If you don't
care about hyper-optimising for power consumption (ie, you're not a
phone), then I bet you could get away with ath9k model hardware. Those
same lower end CPUs can do 200kpps on an ethernet NIC right now. The
reordering and retransmit stuff could be handled in firmware, but
that's about it - and again, only if you wanted to do it on some
anenmic SoC or you cared about power.

People keep talking about "oh god, these things do so much now" - but
that's because people are thinking about phones or those L2-cache-less
anemic older SOCs that are massively memory bandwidth constrained.
Newer stuff is much less terrible.



-adrian

  reply	other threads:[~2016-03-12 20:18 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-11 18:17 [Make-wifi-fast] " Dave Taht
2016-03-11 18:22 ` [Make-wifi-fast] [Cerowrt-devel] " Luis E. Garcia
2016-03-11 19:07   ` Jonathan Morton
2016-03-11 19:31     ` [Make-wifi-fast] [bufferbloat-fcc-discuss] " Paul Vixie
2016-03-11 20:26     ` [Make-wifi-fast] " Alan Jenkins
2016-03-11 20:40       ` David Lang
2016-03-12  9:38         ` Jonathan Morton
2016-03-13  0:15           ` David Lang
2016-03-13 15:18             ` Jonathan Morton
2016-03-13 17:40               ` moeller0
2016-03-13 18:17                 ` Jonathan Morton
2016-03-13 18:25                   ` moeller0
2016-03-13 20:15                     ` Jonathan Morton
2016-03-13 21:17                       ` moeller0
     [not found]               ` <CAEfCu-p+87PkRrN-=9=-CA3JpQesRU2RDmxN-yEJt_95Au-yxA@mail.gmail.com>
2016-03-13 17:48                 ` [Make-wifi-fast] [bufferbloat-fcc-discuss] " Dave Taht
2016-03-13 18:23                   ` [Make-wifi-fast] [Cerowrt-devel] [bufferbloat-fcc-discuss] " moeller0
2016-03-13 23:22                 ` [Make-wifi-fast] [bufferbloat-fcc-discuss] [Cerowrt-devel] " David Lang
     [not found]                   ` <CAEfCu-o7hb+6O0NNc4oUrn7noaVvBhBJK3zNjB8mWtgVtkqpZg@mail.gmail.com>
2016-03-14  1:03                     ` David Lang
     [not found] ` <CAEfCu-rQN+H7h0OY_3CSrrGcVZ=A4=b0XTAU2h3Pz3_ksh56dw@mail.gmail.com>
2016-03-12 19:14   ` [Make-wifi-fast] [bufferbloat-fcc-discuss] " Henning Rogge
2016-03-12 20:18     ` Adrian Chadd [this message]
     [not found]       ` <CAEfCu-rmR=p1bAGJjPvaMMBAjKRU1wBeZW4ZQCZVm5eVXCCRQQ@mail.gmail.com>
2016-03-12 22:20         ` Dave Taht
2016-03-13  1:04       ` David Lang
     [not found]         ` <CAEfCu-r-C3C6P2LpKJduvX733YnbwxBF6nOFAPEMbF28qjRXBg@mail.gmail.com>
2016-03-13  8:06           ` David Lang
2016-03-14  0:51         ` Adrian Chadd
2016-03-14  1:25           ` David Lang
2016-03-13 18:19       ` Dave Taht
2016-03-13  1:00   ` David Lang
2016-03-13 13:25 Brandon Butterworth
2016-03-13 23:20 ` David Lang

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/make-wifi-fast.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJ-Vmo=_zKnmN=yxDuTrKMPR_2gk+d1kzT0bsZYewTSMXCkcCg@mail.gmail.com' \
    --to=adrian@freebsd.org \
    --cc=bufferbloat-fcc-discuss@lists.redbarn.org \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=hrogge@gmail.com \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    --cc=wayne.workman2012@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