From: Aaron Wood <woody77@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Noah Causin <n0manletter@gmail.com>,
make-wifi-fast@lists.bufferbloat.net,
Simon Wunderlich <sw@simonwunderlich.de>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
Felix Fietkau <nbd@nbd.name>
Subject: Re: [Cerowrt-devel] [Make-wifi-fast] wifi airtime fairness patches could use eyeballs and testing
Date: Sun, 14 Aug 2016 15:49:12 -0700 [thread overview]
Message-ID: <CALQXh-Oy_vmVCdURJJw=Fsx5L0q_aT787pAgMezuBZZCPvsrJw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7cK6Cg1a5uN=d3u4x3RNM_ZSuiCLK4ig9+TY71iZadsg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 478 bytes --]
On Sun, Aug 14, 2016 at 3:21 PM, Dave Taht <dave.taht@gmail.com> wrote:
>
> Ideas as to why crypto chops off so much throughput in the first place
> (from 120mbit to 80), and as to what else to poke into with crypto on,
> would be nice.
Crypto as in WPA2? If 1 client is fine, but multiple clients is not, my
guess is that changing the AES key in the crypto accelerator is
slow/difficult, and so what you're seeing is the lost time as it switches
security contexts.
-Aaron
[-- Attachment #2: Type: text/html, Size: 877 bytes --]
next prev parent reply other threads:[~2016-08-14 22:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-10 11:28 [Cerowrt-devel] " Dave Taht
2016-08-10 13:06 ` [Cerowrt-devel] [Make-wifi-fast] " Noah Causin
2016-08-10 13:11 ` Dave Taht
2016-08-10 15:04 ` Toke Høiland-Jørgensen
2016-08-10 19:35 ` Dave Taht
2016-08-10 20:06 ` Toke Høiland-Jørgensen
2016-08-10 21:50 ` Toke Høiland-Jørgensen
2016-08-10 21:58 ` Dave Taht
2016-08-10 22:05 ` Toke Høiland-Jørgensen
2016-08-10 22:07 ` Toke Høiland-Jørgensen
2016-08-10 22:18 ` Jonathan Morton
2016-08-10 22:45 ` Toke Høiland-Jørgensen
2016-08-11 6:43 ` Dave Taht
2016-08-11 9:16 ` Toke Høiland-Jørgensen
2016-08-14 22:21 ` Dave Taht
2016-08-14 22:49 ` Aaron Wood [this message]
2016-08-14 23:02 ` Dave Taht
2016-08-14 23:04 ` Aaron Wood
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-Oy_vmVCdURJJw=Fsx5L0q_aT787pAgMezuBZZCPvsrJw@mail.gmail.com' \
--to=woody77@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=n0manletter@gmail.com \
--cc=nbd@nbd.name \
--cc=sw@simonwunderlich.de \
/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