From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH v3] fm10k: cleanup fm10k stats and remove debug-statistics
Date: Wed, 02 Mar 2016 15:45:30 -0800 [thread overview]
Message-ID: <1456962330.2822.31.camel@intel.com> (raw)
In-Reply-To: <1456951531-15783-1-git-send-email-jacob.e.keller@intel.com>
On Wed, 2016-03-02 at 12:45 -0800, Jacob Keller wrote:
> This change fixes up subtle issues with the current fm10k ethtool
> stats.
> Primarily, support of debug-statistics and per-queue length
> statistics
> is not something the current API can handle. Due to the way that
> ethtool
> works, the number of statistics needs to be static for the life time
> of
> a given device. Our use of debug-statistics does not really allow for
> this, so this patch drops its use.
>
> Finish this cleanup by reworking the per-queue stats to use the new
> helper functions which reduce the duplicate and error prone code.
>
> Signed-off-by: Jacob Keller <jacob.e.keller@intel.com>
> ---
>
> Notes:
> ??? - v3
> ??? * based on comments upstream, make queues static
> ??? * remove debug-statistics support since this can break the
> ethtool API
> ????
> ??? - v4
> ??? * remove extra debug stats strings forgotten in previous rework
>
> This is based on the fact that the ethtool API cannot really support
> variable statistics lengths.
>
> ?drivers/net/ethernet/intel/fm10k/fm10k_ethtool.c | 127 ++++++-------
> ----------
> ?1 file changed, 33 insertions(+), 94 deletions(-)
This patch does not apply cleanly. ?I tried looking to see if I have
the previous patch applied and it does not appear that I do, unless you
changed the patch title (which is not the first time you done something
like this :-()
Looks like a v5 is needed or you let me know what patch this is
replacing in my current tree.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.osuosl.org/pipermail/intel-wired-lan/attachments/20160302/4f12c62d/attachment.asc>
next prev parent reply other threads:[~2016-03-02 23:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 20:45 [Intel-wired-lan] [PATCH v3] fm10k: cleanup fm10k stats and remove debug-statistics Jacob Keller
2016-03-02 22:48 ` Jeff Kirsher
2016-03-02 22:55 ` Keller, Jacob E
2016-03-02 23:45 ` Jeff Kirsher [this message]
2016-03-03 0:06 ` Keller, Jacob E
-- strict thread matches above, loose matches on Subject: below --
2016-03-02 20:23 Jacob Keller
2016-03-02 20:28 ` Keller, Jacob E
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=1456962330.2822.31.camel@intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=intel-wired-lan@osuosl.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