From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from wolverine01.qualcomm.com ([199.106.114.254]) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1asXgj-0001NG-JW for ath10k@lists.infradead.org; Tue, 19 Apr 2016 15:35:43 +0000 From: "Valo, Kalle" Subject: Re: ath10k performance, master branch from 20160407 Date: Tue, 19 Apr 2016 15:35:16 +0000 Message-ID: <87k2jtk3wt.fsf@kamboji.qca.qualcomm.com> References: <1460129643950.46282@qti.qualcomm.com> <1460174525702.66744@qti.qualcomm.com> <1460905574286.42282@qti.qualcomm.com> In-Reply-To: (Michal Kazior's message of "Tue, 19 Apr 2016 09:43:31 +0200") Content-Language: en-US Content-ID: <217694A695739F4A90C78049F6126C77@qualcomm.com> MIME-Version: 1.0 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "ath10k" Errors-To: ath10k-bounces+kvalo=adurom.com@lists.infradead.org To: "michal.kazior@tieto.com" Cc: Roman Yeryomin , "Manoharan, Rajkumar" , "ath10k@lists.infradead.org" , Rajkumar Manoharan Michal Kazior writes: > On 19 April 2016 at 09:31, Roman Yeryomin wrote: >> On 19 April 2016 at 08:28, Michal Kazior wrote: >> >>> If my hunch is right there's no easy (and proper) fix for that now. >>> >>> One of the patchset patches (ath10k: implement wake_tx_queue) starts >>> to use mac80211 software queuing. This introduces extra induced >>> latency and I'm guessing it results in fill-in-then-drain sequences in >>> some cases which end up being long enough to make fq_codel_drop more >>> work than normal. >>> >>> This is required for other changes and MU-MIMO performance >>> improvements so this patch can't be removed. >> >> But qca988x doesn't support MU-MIMO, AFAIK. > > Correct. > > >> Can this be made chip dependent? > > I guess it could but it'd arguably make the driver more complex and > harder to maintain. What we want is a long-term fix, not a short-term > one. But we should never go backwards and TCP dropping from 750 Mbps to ~550 Mbps is a huge drop, so this is not ok. We have to do something to fix this, be it reverting the wake_tx_queue support, somehow disabling it by default or something. -- Kalle Valo _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k