From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail.toke.dk ([52.28.52.200]:34327 "EHLO mail.toke.dk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751261AbdBLQgo (ORCPT ); Sun, 12 Feb 2017 11:36:44 -0500 From: =?utf-8?Q?Toke_H=C3=B8iland-J=C3=B8rgensen?= To: Felix Fietkau Cc: Kalle Valo , linux-wireless@vger.kernel.org Subject: Re: [PATCH] ath9k: clean up and fix ath_tx_count_airtime References: <20170212132931.43510-1-nbd@nbd.name> <87lgtb5t9h.fsf@alrua-karlstad> <87d1entltw.fsf@kamboji.qca.qualcomm.com> <61049ab3-a15e-b1cf-ca1d-4840a8aa35d9@nbd.name> Date: Sun, 12 Feb 2017 17:36:39 +0100 In-Reply-To: <61049ab3-a15e-b1cf-ca1d-4840a8aa35d9@nbd.name> (Felix Fietkau's message of "Sun, 12 Feb 2017 17:32:35 +0100") Message-ID: <87efz35pt4.fsf@alrua-karlstad> (sfid-20170212_173646_818983_A29C85AF) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: Felix Fietkau writes: > On 2017-02-12 17:28, Kalle Valo wrote: >> Felix Fietkau writes: >>=20 >>> On 2017-02-12 16:22, Toke H=C3=B8iland-J=C3=B8rgensen wrote: >>>> Felix Fietkau writes: >>>>=20 >>>>> ath_tx_count_airtime is doing a lot of unnecessary work: >>>>> >>>>> - Redundant station lookup >>>>> - Redundant rcu_read_lock/unlock >>>>> - Useless memcpy of bf->rates >>>>> - Useless NULL check of bf->bf_mpdu >>>>> - Redundant lookup of the skb tid >>>>> >>>>> Additionally, it tries to look up the mac80211 queue index from the t= xq, >>>>> which fails if the frame was delivered via the power save queue. >>=20 >> What does this mean in practise, what's the user level impact? >>=20 >>>>> This patch fixes all of these issues by passing down the right set of >>>>> pointers instead of doing extra work >>>>> >>>>> Cc: stable@vger.kernel.org >>>>> Fixes: 63fefa050477 ("ath9k: Introduce airtime fairness scheduling >>>>> between stations") >>>>> Signed-off-by: Felix Fietkau >>>>=20 >>>> Not sure if there's anything for stable to do with this; don't think t= he >>>> airtime fairness code has gone into a release yet? Otherwise: >>>>=20 >>>> Acked-by: Toke H=C3=B8iland-J=C3=B8rgensen >>> >>> I added this, because I'm not sure this patch will make it to 4.10 in >>> time, since we're really close to a release. I assume this patch will >>> probably go into 4.11. >>=20 >> Yeah, to try to get a patch to 4.10 at this point needs to be a really >> high profile regression. That is if Linus doesn't release 4.10 today, of >> course. > The symptoms are kernel crashes at least when operating in AP mode. > It's pretty severe, so getting it into 4.10 would be preferable. I'm confused now. Wasn't the airtime fairness patch queued for 4.11? -Toke