From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.toke.dk (mail.toke.dk [52.28.52.200]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 0FC993B2A4 for ; Wed, 19 Dec 2018 08:13:02 -0500 (EST) From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1545225149; bh=ue5HP6/E/M6QMPht6KAfJl+qYK3AK+eVPMfbdQLXZ8s=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=yRyNa0zU9D+PXKlCV4sHnRUc2S94iK60ftlVfD1gAS02drA1QFtuu1c4hGEOCdDTx NWHfOTsVCOZKDieJ+VJgLjN/s2oj/zCI/XoDmmu4EWPHC7kfmkvGbUlPYOnVKmW2+F JL2nTKVCvzNWzEvREaJ5GjwV4jThHabdIw+Un4gAgI/nqjkXTt2OSKXxJ8qDDKnxDU oyhf34Tkuy2JU0m2nOK8zlVqwpTVut8MG8SaShsxtlSld5YZ0m7JQPoZVFHHcB3b/p vIdSliNqR6uVNYL1/WqacFD/H32B+Y3MegHwa7WNZbSu7BGew6vAlI8kjX/I5CNIGz +q111gdjHdA0A== To: Rajkumar Manoharan , linux-wireless@vger.kernel.org, ath10k@lists.infradead.org, Johannes Berg Cc: make-wifi-fast@lists.bufferbloat.net, Rajkumar Manoharan In-Reply-To: <1545181331-5288-1-git-send-email-rmanohar@codeaurora.org> References: <1545181331-5288-1-git-send-email-rmanohar@codeaurora.org> Date: Wed, 19 Dec 2018 14:12:27 +0100 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <877eg5hd8k.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Make-wifi-fast] [PATCH v5 0/6] Move TXQ scheduling and airtime fairness into mac80211 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, 19 Dec 2018 13:13:02 -0000 Rajkumar Manoharan writes: > All, > > Sorry for the long delay. Here is the consolidated series of mac80211, > ath9k and ath10k changes for moving TXQ scheduling and airtime fairness > into mac80211 and support airtime fairness. Thanks for taking care of the respin! Johannes, I think it's safe for you to review this version. I have started working on another approach for the scheduler algorithm itself, but it is fine to do as an incremental patch on top of this as it shouldn't impact the API. Having a separate patch also makes testing easier anyway. I'll see if I can't get it to a working state over the holidays... -Toke