From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail2.candelatech.com ([208.74.158.173]) by merlin.infradead.org with esmtp (Exim 4.85 #2 (Red Hat Linux)) id 1al0Ao-0000AH-4j for ath10k@lists.infradead.org; Tue, 29 Mar 2016 20:23:34 +0000 Received: from [192.168.100.149] (firewall.candelatech.com [50.251.239.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail2.candelatech.com (Postfix) with ESMTPSA id D4ECA40EB1F for ; Tue, 29 Mar 2016 12:26:14 -0700 (PDT) From: Ben Greear Subject: How is tx-flushing supposed to work now? Message-ID: <56FAD6D6.9030105@candelatech.com> Date: Tue, 29 Mar 2016 12:26:14 -0700 MIME-Version: 1.0 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: "ath10k" Errors-To: ath10k-bounces+kvalo=adurom.com@lists.infradead.org To: ath10k When we have multiple vdevs, and the 10.4.3 firmware with the tx-push logic, how is flushing supposed to work? First, when we get a flush, should we first purge any frames not yet pushed to the firmware? And second, what keeps other vdevs from continuing to transmit frames while one vdev is trying to be flushed? Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k