From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>, netdev@vger.kernel.org
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [PATCH 1/3] ethtool: Support ETHTOOL_GSTATS2 command.
Date: Thu, 19 Apr 2018 17:26:57 +0200 [thread overview]
Message-ID: <1524151617.3024.25.camel@sipsolutions.net> (raw)
In-Reply-To: <173c5f98-36bc-2e52-1e64-3a5f89008d46@candelatech.com>
On Thu, 2018-04-19 at 08:25 -0700, Ben Greear wrote:
>
> In order to efficiently parse lots of stats over and over again, I probe
> the stat names once on startup, map them to the variable I am trying to use
> (since different drivers may have different names for the same basic stat),
> and then I store the stat index.
>
> On subsequent stat reads, I just grab stats and go right to the index to
> store the stat.
>
> If the stats indexes change, that will complicate my logic quite a bit.
That's a good point.
> Maybe the flag could be called: ETHTOOL_GS2_NO_REFRESH_FW ?
Sounds more to the point to me, yeah.
> >
> > Also, wrt. the rest of the patch, I'd argue that it'd be worthwhile to
> > write the spatch and just add the flags argument to "get_ethtool_stats"
> > instead of adding a separate method - internally to the kernel it's not
> > that hard to change.
>
> Maybe this could be in followup patches? It's going to touch a lot of files,
> and might be hell to get merged all at once, and I've never used spatch, so
> just maybe someone else will volunteer that part :)
I guess you'll have to ask davem. :)
johannes
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2018-04-19 15:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 1:49 [PATCH 1/3] ethtool: Support ETHTOOL_GSTATS2 command greearb
2018-04-18 1:49 ` [PATCH 2/3] mac80211: Add support for ethtool gstats2 API greearb
2018-04-18 1:49 ` [PATCH 3/3] ath10k: Support " greearb
2018-04-19 11:19 ` kbuild test robot
2018-04-18 21:07 ` [PATCH 1/3] ethtool: Support ETHTOOL_GSTATS2 command Florian Fainelli
2018-04-18 21:26 ` Johannes Berg
2018-04-18 21:51 ` Ben Greear
2018-04-19 6:38 ` Johannes Berg
2018-04-19 15:25 ` Ben Greear
2018-04-19 15:26 ` Johannes Berg [this message]
2018-04-22 18:54 ` David Miller
2018-04-22 21:15 ` Roopa Prabhu
2018-04-23 15:41 ` Ben Greear
2018-04-23 15:38 ` Ben Greear
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=1524151617.3024.25.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ath10k@lists.infradead.org \
--cc=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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