[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230113204336.401a2062@kernel.org>
Date: Fri, 13 Jan 2023 20:43:36 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Vladimir Oltean <vladimir.oltean@....com>
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Paolo Abeni <pabeni@...hat.com>,
Michal Kubecek <mkubecek@...e.cz>,
Claudiu Manoil <claudiu.manoil@....com>,
Vinicius Costa Gomes <vinicius.gomes@...el.com>,
Xiaoliang Yang <xiaoliang.yang_1@....com>,
Kurt Kanzenbach <kurt@...utronix.de>,
Rui Sousa <rui.sousa@....com>,
Ferenc Fejes <ferenc.fejes@...csson.com>,
Pranavi Somisetty <pranavi.somisetty@....com>,
Harini Katakam <harini.katakam@....com>,
Colin Foster <colin.foster@...advantage.com>,
UNGLinuxDriver@...rochip.com,
Alexandre Belloni <alexandre.belloni@...tlin.com>,
Andrew Lunn <andrew@...n.ch>,
Florian Fainelli <f.fainelli@...il.com>
Subject: Re: [PATCH v2 net-next 04/12] net: ethtool: netlink: retrieve stats
from multiple sources (eMAC, pMAC)
On Wed, 11 Jan 2023 18:16:58 +0200 Vladimir Oltean wrote:
> +/**
> + * enum ethtool_stats_src - source of ethtool statistics
> + * @ETHTOOL_STATS_SRC_AGGREGATE:
> + * if device supports a MAC merge layer, this retrieves the aggregate
> + * statistics of the eMAC and pMAC. Otherwise, it retrieves just the
> + * statistics of the single (express) MAC.
> + * @ETHTOOL_STATS_SRC_EMAC:
> + * if device supports a MM layer, this retrieves the eMAC statistics.
> + * Otherwise, it retrieves the statistics of the single (express) MAC.
> + * @ETHTOOL_STATS_SRC_PMAC:
> + * if device supports a MM layer, this retrieves the pMAC statistics.
> + */
> +enum ethtool_stats_src {
> + ETHTOOL_STATS_SRC_AGGREGATE,
> + ETHTOOL_STATS_SRC_EMAC,
> + ETHTOOL_STATS_SRC_PMAC,
> +};
Should we somehow call it "MAC stats"?
Right now its named like a generic attribute, but it's not part of
the header nest (ETHTOOL_A_HEADER_*).
I'm not sure myself which way is better, but feels like either it
should be generic, in the header nest, and parsed by the common code;
or named more specifically and stay in the per-cmd attrs.
Powered by blists - more mailing lists