From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ua0-x232.google.com (mail-ua0-x232.google.com [IPv6:2607:f8b0:400c:c08::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 95C673B2A0; Sun, 14 Aug 2016 19:04:14 -0400 (EDT) Received: by mail-ua0-x232.google.com with SMTP id n59so52703227uan.2; Sun, 14 Aug 2016 16:04:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=7By35ZZXm4HQBeYTFPc9yuY2M4nHci4idmlwA+v7JEU=; b=wGdeuseLTip7y2a7yZ+qqk+XI232bOGeFLx3/hR9AWifoPhr7/o9a55RrTIit9vR4n bPyalzmKVK6LfUCT431Eb1gLX2ewY+Sv7lfYOtbBo2KkzUl8vkbJPLkMyDW++TNwE0BT h4GtWT1IsPPCi3bw7mERdvuA/eFpDbzhSzhQ3HV7hx1zyuxnt48XSG+W3OSm0Hyvk5qv FAVO1L8tNBkUSgsWkC4SaTHXWMxN0+BWa5Y2CYDFtuAKywNJp1DdQt7JhwQefLcCVpXK /QlVvE9W1VnLY9oU2GXOK/QbglKNuE52m6tX63j98Pq2AMpPjHdZuYf1agqlStBRVAXX JbXA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=7By35ZZXm4HQBeYTFPc9yuY2M4nHci4idmlwA+v7JEU=; b=On8UIXaJYzKpumJJhZKDuHkrPks88cIOE/YSBq1p367gubsbdWyrkHab/PQGM1uQce xAz+V3xIcqIdU32mwhXdZRWv5XiYSuhCUqvhiPAbGjDhVTeuq/5FGmITsL72sTXjICRN 9Zm/2VmEvpCFDSl/0i5D28fn5yD5p/UrhlxnLj+2SPxlTXps8MMP+Dmg7JeUpKEXJNSm K6VWyzwM/hxcGYBK27yJdhX/kbFzwlOMOtnegK8S+KNo3iZ0p8aV3gZqQqhfl8+lNHZx eGopXO2+4i953nL1qKUivMqVC/RftHIKUDfgDSned3EPSuWFPLwk/ewaPevHXYOI7Qe5 yDVg== X-Gm-Message-State: AEkoouuN9thySCA5TjLfTyRWHdKMXPks2nwDJv7cNj7RhUh7SusdActfs+pIaubsBsdj/hv/G3p22g8ZZlKyyQ== X-Received: by 10.31.9.67 with SMTP id 64mr12434663vkj.89.1471215853995; Sun, 14 Aug 2016 16:04:13 -0700 (PDT) MIME-Version: 1.0 Received: by 10.103.120.23 with HTTP; Sun, 14 Aug 2016 16:04:13 -0700 (PDT) In-Reply-To: References: <76eb6a6a-2f39-3b36-d4c1-04198083c0f6@gmail.com> From: Aaron Wood Date: Sun, 14 Aug 2016 16:04:13 -0700 Message-ID: To: Dave Taht Cc: Noah Causin , make-wifi-fast@lists.bufferbloat.net, Simon Wunderlich , "cerowrt-devel@lists.bufferbloat.net" , Felix Fietkau Content-Type: multipart/alternative; boundary=001a11440ef45d8b70053a10224c Subject: Re: [Cerowrt-devel] [Make-wifi-fast] wifi airtime fairness patches could use eyeballs and testing X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Aug 2016 23:04:14 -0000 --001a11440ef45d8b70053a10224c Content-Type: text/plain; charset=UTF-8 On Sun, Aug 14, 2016 at 4:02 PM, Dave Taht wrote: > On Mon, Aug 15, 2016 at 12:49 AM, Aaron Wood wrote: > > On Sun, Aug 14, 2016 at 3:21 PM, Dave Taht 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. > > 1 client suffers degradation with more than one flow in flight, being > fq'd, and crypted with wpa2. > > I'll have plots in the morning. > So it's not, that, then. Unless it's doing something dumb with the keys when it switches flows (since that's now an interrupt back up to the driver?) -Aaron --001a11440ef45d8b70053a10224c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Sun, Aug 14, 2016 at 4:02 PM, Dave Taht <dave.taht@g= mail.com> wrote:
On Mon, Aug 15= , 2016 at 12:49 AM, Aaron Wood <woo= dy77@gmail.com> wrote:
> 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 p= lace
>> (from 120mbit to 80), and as to what else to poke into with crypto= on,
>> would be nice.
>
>
> Crypto as in WPA2?=C2=A0 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 s= witches
> security contexts.

1 client suffers degradation with more than one flow in flight, bein= g
fq'd, and crypted with wpa2.

I'll have plots in the morning.

So = it's not, that, then.=C2=A0 Unless it's doing something dumb with t= he keys when it switches flows (since that's now an interrupt back up t= o the driver?)

-Aaron=C2=A0
--001a11440ef45d8b70053a10224c--