From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from sipsolutions.net (s3.sipsolutions.net [5.9.151.49]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id E106E3B2A0 for ; Wed, 17 Aug 2016 09:18:16 -0400 (EDT) Received: by sipsolutions.net with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.87) (envelope-from ) id 1ba0jX-0008QL-QB; Wed, 17 Aug 2016 15:18:15 +0200 Message-ID: <1471439894.5173.9.camel@sipsolutions.net> From: Johannes Berg To: Toke =?ISO-8859-1?Q?H=F8iland-J=F8rgensen?= Cc: make-wifi-fast@lists.bufferbloat.net, linux-wireless@vger.kernel.org, Felix Fietkau Date: Wed, 17 Aug 2016 15:18:14 +0200 In-Reply-To: <87h9aj5ydx.fsf@toke.dk> References: <20160817125800.19154-1-toke@toke.dk> <1471439315.5173.7.camel@sipsolutions.net> <87h9aj5ydx.fsf@toke.dk> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.20.4-1+b1 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: Re: [Make-wifi-fast] [PATCH] mac80211: Move crypto IV generation to after TXQ dequeue. X-BeenThere: make-wifi-fast@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Aug 2016 13:18:17 -0000 On Wed, 2016-08-17 at 15:16 +0200, Toke Høiland-Jørgensen wrote: > Johannes Berg writes: > > > > > > > > > @@ -1573,6 +1574,7 @@ struct ieee80211_key_conf { > > >   u8 iv_len; > > >   u8 hw_key_idx; > > >   u8 flags; > > > + u8 pn_offs; > > > > > This is completely wrong. > > Well, the ieee80211_fast_tx struct is not available in > ieee80211_tx_dequeue, and I need the offset there. I thought about > sticking it into ieee80211_tx_info, but that is kinda full, and since > the ieee80211_key_conf is already available there, carrying it there > seems to work. For very limited testing, perhaps. But this isn't static across all usages of the key, so this is still completely broken. > What would be a better way to do this? > Some redesign/rearchitecture, probably. Or just do it all in the driver like iwlmvm? johannes