Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 380EEECDE43 for ; Fri, 19 Oct 2018 17:34:23 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id EFABE2087A for ; Fri, 19 Oct 2018 17:34:22 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org EFABE2087A Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=candelatech.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-wireless-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727501AbeJTBlY (ORCPT ); Fri, 19 Oct 2018 21:41:24 -0400 Received: from mail2.candelatech.com ([208.74.158.173]:42618 "EHLO mail2.candelatech.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727188AbeJTBlX (ORCPT ); Fri, 19 Oct 2018 21:41:23 -0400 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 0C5D140A5A2 for ; Fri, 19 Oct 2018 10:34:19 -0700 (PDT) To: "linux-wireless@vger.kernel.org" From: Ben Greear Subject: Where to report mpdus tx vs failed? Organization: Candela Technologies Message-ID: <104c8823-e867-6244-a528-979482c7fccc@candelatech.com> Date: Fri, 19 Oct 2018 10:34:18 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org While debugging rate-ctrl in ath10k, I found the amount of mpdus transmitted vs failed ratio useful. Probably more useful than retries since retries could count an attempt at 80Mhz followed by HW trying a 40Mhz rate (afaik). Is there a good way to report this up the stack in a useful manner? I currently only get this stat for the first frame in an transmitted ampdu. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com