From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Ben Greear <greearb@candelatech.com>
Cc: ath10k <ath10k@lists.infradead.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Reporting firmware stats to ethtool
Date: Fri, 8 Aug 2014 12:06:15 +0300 [thread overview]
Message-ID: <87wqajz6yg.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <53E3F65D.8080102@candelatech.com> (Ben Greear's message of "Thu, 07 Aug 2014 14:57:49 -0700")
Ben Greear <greearb@candelatech.com> writes:
> 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.
I also prefer to have this in user space, but how does user space know
when the stats have been zeroed?
--
Kalle Valo
next prev parent reply other threads:[~2014-08-08 9:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 21:57 Reporting firmware stats to ethtool Ben Greear
2014-08-08 9:06 ` Kalle Valo [this message]
2014-08-08 15:42 ` Ben Greear
2014-08-08 15:55 ` Dave Taht
2014-08-08 16:11 ` Ben Greear
2014-08-08 16:45 ` Arend van Spriel
2014-08-08 17:24 ` Ben Greear
2014-08-09 6:32 ` Kalle Valo
2014-08-09 6:30 ` Kalle Valo
2014-08-09 7:30 ` Arend van Spriel
2014-08-09 15:56 ` 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=87wqajz6yg.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=greearb@candelatech.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).