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-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 3691E3B2D2; Tue, 19 Apr 2016 05:10:22 -0400 (EDT) Received: by sipsolutions.net with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.87) (envelope-from ) id 1asRfo-0002Wk-9z; Tue, 19 Apr 2016 11:10:20 +0200 Message-ID: <1461057018.2766.14.camel@sipsolutions.net> From: Johannes Berg To: Michal Kazior , Eric Dumazet Cc: make-wifi-fast@lists.bufferbloat.net, linux-wireless , codel@lists.bufferbloat.net, Avery Pennarun Date: Tue, 19 Apr 2016 11:10:18 +0200 In-Reply-To: (sfid-20160418_153625_392021_99464B1E) References: <1459420104-31554-1-git-send-email-michal.kazior@tieto.com> <1460636302-31161-1-git-send-email-michal.kazior@tieto.com> <1460636302-31161-3-git-send-email-michal.kazior@tieto.com> <1460845384.2075.27.camel@sipsolutions.net> <1460845552.2075.28.camel@sipsolutions.net> <1460982672.10638.111.camel@edumazet-glaptop3.roam.corp.google.com> (sfid-20160418_153625_392021_99464B1E) Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.18.5.1-1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [Codel] [PATCHv3 2/5] mac80211: implement fair queueing per txq X-BeenThere: codel@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: CoDel AQM discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 09:10:22 -0000 On Mon, 2016-04-18 at 15:36 +0200, Michal Kazior wrote: > FWIW cfg80211 drivers might become another user of the fq/codel stuff > in the future. > > Arguably I should make include/net/codel.h not be qdisc specific as > it is now (and hence re-usable by mac80211) and submit fq.h to > include/net/. Would that be better (it'll probably take a lot longer > to propagate over trees, no?) I think it would be better, and we could sync and take it through my tree, or I can sync and just pull back davem's tree once it's there; I don't think code "management" wise it'll be an issue. > johannes