All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: ath10k <ath10k@lists.infradead.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Reporting firmware stats to ethtool
Date: Thu, 07 Aug 2014 14:57:49 -0700	[thread overview]
Message-ID: <53E3F65D.8080102@candelatech.com> (raw)

I'm working on a patch to report the stats seen in debugfs/...ath10k/fw_stats
as ethtool stats, somewhat similar to how ath9k does it.

I notice that my user-space tool is reporting huge numbers because
the stats are reset to zero when firmware restarts, and so my tool
thinks the stats wrapped.

I can fix my tool easily enough, but I first wanted to see if
anyone had strong feelings about keeping the stats from resetting
to zero by storing history and calculating diffs in the driver.

I think my preference is to punt this to user-space, but if
someone feels otherwise, please let me know sooner than later.

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

WARNING: multiple messages have this Message-ID (diff)
From: Ben Greear <greearb@candelatech.com>
To: ath10k <ath10k@lists.infradead.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Reporting firmware stats to ethtool
Date: Thu, 07 Aug 2014 14:57:49 -0700	[thread overview]
Message-ID: <53E3F65D.8080102@candelatech.com> (raw)

I'm working on a patch to report the stats seen in debugfs/...ath10k/fw_stats
as ethtool stats, somewhat similar to how ath9k does it.

I notice that my user-space tool is reporting huge numbers because
the stats are reset to zero when firmware restarts, and so my tool
thinks the stats wrapped.

I can fix my tool easily enough, but I first wanted to see if
anyone had strong feelings about keeping the stats from resetting
to zero by storing history and calculating diffs in the driver.

I think my preference is to punt this to user-space, but if
someone feels otherwise, please let me know sooner than later.

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


             reply	other threads:[~2014-08-07 21:58 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-07 21:57 Ben Greear [this message]
2014-08-07 21:57 ` Reporting firmware stats to ethtool Ben Greear
2014-08-08  9:06 ` Kalle Valo
2014-08-08  9:06   ` Kalle Valo
2014-08-08 15:42   ` Ben Greear
2014-08-08 15:42     ` Ben Greear
2014-08-08 15:55     ` Dave Taht
2014-08-08 15:55       ` Dave Taht
2014-08-08 16:11       ` Ben Greear
2014-08-08 16:11         ` Ben Greear
2014-08-08 16:45         ` Arend van Spriel
2014-08-08 16:45           ` Arend van Spriel
2014-08-08 17:24           ` Ben Greear
2014-08-08 17:24             ` Ben Greear
2014-08-09  6:32             ` Kalle Valo
2014-08-09  6:32               ` Kalle Valo
2014-08-09  6:30           ` Kalle Valo
2014-08-09  6:30             ` Kalle Valo
2014-08-09  7:30             ` Arend van Spriel
2014-08-09  7:30               ` Arend van Spriel
2014-08-09 15:56               ` Kalle Valo
2014-08-09 15:56                 ` Kalle Valo
2014-08-09  6:27     ` Kalle Valo
2014-08-09  6:27       ` Kalle Valo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53E3F65D.8080102@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ath10k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.