Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp445455ybl; Tue, 20 Aug 2019 23:35:32 -0700 (PDT) X-Google-Smtp-Source: APXvYqzF7AI6R2MO50vcg2pWG4LhrVmut30i0RzFuv89hKWCG/i3xr6i1qai5cHX5Ip9PvlLrg1h X-Received: by 2002:a63:9318:: with SMTP id b24mr27744005pge.31.1566369332719; Tue, 20 Aug 2019 23:35:32 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566369332; cv=none; d=google.com; s=arc-20160816; b=TvG5+RxHnIFaiIULc0XkiEq1jrWsQwhAtPDI8YIK2S1NJJC1cj66iEEqvIfbtWPGlG QHPA6CMP4+YbgrWrDBAacEp9K0Y6cz8ZxIq4G0MAQDHSbz2fI/fk1+8XBQZoyzu3XZIT jUVj8hAiXHdZFTWhZfzg6I+SkGOWA6BI2q3eWqvTbgBAwTgNbp0r34sj0d9esCQS0Hi7 JtT2/1xoUgYhy1gNL/orzPGViUfyk+iSY1YpGLBrdoAxIzhYIPGcr4xe7o+eBwyZnGOr 0opxX2Dok7usLcz5PY+78ZebOefhaKAr23OKmvK5o04OFXv5kFdW6CqZNsoP/Y8PpETI Fzsw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:content-transfer-encoding :content-language:accept-language:in-reply-to:references:message-id :date:thread-index:cc:to:from:thread-topic:subject:dkim-signature; bh=WBkZXWKm6w/uVqLAawYFur0sYNZA3WC5C6OFy6a7AnA=; b=WhuK/qXrzOqJC2/xL3bajlEUTlg4tGVDNTmwhvf/STuSxseyFugZ5hn5d/B52rmdgk N4x7PvY/eFd5m5ZaIrVZDcTGCYEIYzpbBnFmOaht10mtKXibXN+lxQmk4y5J2RVo+n+b QbcjxEZWKeELo6m/Uyb/cUL97+hkdB/qX8xAulDwGyFMwleqkjIOQYzOOuAFbSqgnnGT g2GGGOcUDe5fxwGlXbzC2GVCRw+Tiijte0WMFU3MqkV3xW5LgNXDW0lMuhEfmHDpbLxE Q5m9O7NFXbROtgcKDVb3iSaGu8wNQz8VwVSgsZVv6kzOP7To1zbbkRErnr5NdCmrIz2Z mMZg== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@qti.qualcomm.com header.s=qcdkim header.b=ua6E30Dr; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=qti.qualcomm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id s38si13628437pgl.138.2019.08.20.23.35.11; Tue, 20 Aug 2019 23:35:32 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@qti.qualcomm.com header.s=qcdkim header.b=ua6E30Dr; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=qti.qualcomm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727929AbfHUGUS (ORCPT + 99 others); Wed, 21 Aug 2019 02:20:18 -0400 Received: from alexa-out-tai-01.qualcomm.com ([103.229.16.226]:59543 "EHLO alexa-out-tai-01.qualcomm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726484AbfHUGUS (ORCPT ); Wed, 21 Aug 2019 02:20:18 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1566368417; x=1597904417; h=from:to:cc:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version:subject; bh=WBkZXWKm6w/uVqLAawYFur0sYNZA3WC5C6OFy6a7AnA=; b=ua6E30DrXaRlL9HWWqdo4oaJBqExPCKMu6JFN+/ahSriLsGBt9rkgLVu yVxGjH+OLoMSGoJ3KkbbViOFw38iW1L0N05Pp2jqfrgIThfONha/bicQ2 vVvFmHCrcJJWz8Ml/J7F+of2vwWGGXt9cJSmP2Wk/bFyz2O3wX04NB++f s=; Subject: RE: [PATCH 4/7] ath10k: disable TX complete indication of htt for sdio Thread-Topic: [PATCH 4/7] ath10k: disable TX complete indication of htt for sdio Received: from ironmsg02-tai.qualcomm.com ([10.249.140.7]) by alexa-out-tai-01.qualcomm.com with ESMTP; 21 Aug 2019 14:20:16 +0800 Received: from aptaiexm02f.ap.qualcomm.com ([10.249.150.16]) by ironmsg02-tai.qualcomm.com with ESMTP/TLS/AES256-SHA; 21 Aug 2019 14:20:11 +0800 Received: from aptaiexm02f.ap.qualcomm.com (10.249.150.16) by aptaiexm02f.ap.qualcomm.com (10.249.150.16) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 21 Aug 2019 14:20:09 +0800 Received: from aptaiexm02f.ap.qualcomm.com ([fe80::4152:1436:e436:faa1]) by aptaiexm02f.ap.qualcomm.com ([fe80::4152:1436:e436:faa1%19]) with mapi id 15.00.1473.005; Wed, 21 Aug 2019 14:20:09 +0800 From: Wen Gong To: =?iso-8859-1?Q?Toke_H=F8iland-J=F8rgensen?= , Wen Gong , "ath10k@lists.infradead.org" CC: "linux-wireless@vger.kernel.org" Thread-Index: AQHVV1IyEev87vakM0G2WVqJ6I35M6cFHQig Date: Wed, 21 Aug 2019 06:20:09 +0000 Message-ID: <00992d0991704b0fae73a500bb2eb504@aptaiexm02f.ap.qualcomm.com> References: <1566302108-18219-1-git-send-email-wgong@codeaurora.org> <1566302108-18219-5-git-send-email-wgong@codeaurora.org> <87blwkt480.fsf@toke.dk> In-Reply-To: <87blwkt480.fsf@toke.dk> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.80.80.8] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org > -----Original Message----- > From: ath10k On Behalf Of Toke > H=F8iland-J=F8rgensen > Sent: Tuesday, August 20, 2019 8:24 PM > To: Wen Gong ; ath10k@lists.infradead.org > Cc: linux-wireless@vger.kernel.org > Subject: [EXT] Re: [PATCH 4/7] ath10k: disable TX complete indication of = htt > for sdio >=20 > Wen Gong writes: >=20 > > Tx complete message from firmware cost bus bandwidth of sdio, and bus > > bandwidth is the bollteneck of throughput, it will effect the bandwidth > > occupancy of data packet of TX and RX. > > > > This patch disable TX complete indication from firmware for htt data > > packet, it results in significant performance improvement on TX path. >=20 > Wait, how does that work? Am I understanding it correctly that this > replaces a per-packet TX completion with a periodic one sent out of > band? When this patch applied, firmware will not indicate tx complete for tx Data, it only indicate HTT_T2H_MSG_TYPE_TX_CREDIT_UPDATE_IND, This htt msg will tell how many data tx complete without status(status mayb= e success/fail). >=20 > And could you explain what the credits thing is for, please? :) For high latency bus chip, all the tx data's content(include ip/udp/tcp hea= der and payload) will be transfer to firmware's memory via bus. And firmware has limited memory for tx data, the tx data's content must Saved in firmware memory before it tx complete, if ath10k transfer tx data more than the limit, firmware will occur error. The credit is used to avoid ath10k exceed the limit. >=20 > -Toke >=20 > _______________________________________________ > ath10k mailing list > ath10k@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/ath10k