mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Moon Yeounsu <yyyynoom@gmail.com>
Cc: davem@davemloft.net, Eric Dumazet <edumazet@google.com>,
	kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net: dlink: add get_ethtool_stats in ethtool
Date: Tue, 29 Oct 2024 13:53:29 +0100	[thread overview]
Message-ID: <c0cafab5-7a8a-49a4-8d46-a79b47eee867@lunn.ch> (raw)
In-Reply-To: <CAAjsZQwDG8m33yvXRf+ERpziGDxULwyiTTBU4Ph7Rq0MbfqoEQ@mail.gmail.com>

> Regarding the RMON statistics, I understand that you are advising me to use the
> structured ethtool_rmon_stats for RMON statistics and to reserve unstructured
> ethtool -S (without groups) for non-standard statistics. The documentation[1]
> specifies grouping RMON statistics, but there are other statistics in my patch
> that are not part of the RMON. Would it be appropriate to group these
> additional statistics as well?

Groups are used where we expect drivers to offer the same
statistics. Having the group means we have a well defined interface,
where as in the past they were just dumped in ethtool -S, often with
inconsistent names. So once you have extracted the RMON stats, see
what you have left and see if they fit any of the existing groups. If
not, they are probably just what the hardware vendor thought was
useful, rather than being defined by some standard, so can be part of
the unstructured output of ethtool -S.

	Andrew

      parent reply	other threads:[~2024-10-29 12:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-26 19:26 Moon Yeounsu
2024-10-28 12:56 ` Andrew Lunn
2024-10-29  8:30   ` Moon Yeounsu
     [not found]   ` <CAAjsZQwDG8m33yvXRf+ERpziGDxULwyiTTBU4Ph7Rq0MbfqoEQ@mail.gmail.com>
2024-10-29 12:53     ` Andrew Lunn [this message]

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=c0cafab5-7a8a-49a4-8d46-a79b47eee867@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=yyyynoom@gmail.com \
    /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

all inboxes | Powered by JetHome®