From: Jakub Kicinski <kuba@kernel.org>
To: Fan Gong <gongfan1@huawei.com>
Cc: <andrew+netdev@lunn.ch>, <davem@davemloft.net>,
<dimitri.daskalakis1@gmail.com>, <edumazet@google.com>,
<horms@kernel.org>, <hramamurthy@google.com>,
<ioana.ciornei@nxp.com>, <larysa.zaremba@intel.com>,
<linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<maxime.chevallier@bootlin.com>, <mohsin.bashr@gmail.com>,
<netdev@vger.kernel.org>, <pabeni@redhat.com>,
<tengpeisen@huawei.com>, <vadim.fedorenko@linux.dev>,
<wudi234@huawei.com>, <wulike1@huawei.com>,
<zhoushuai28@huawei.com>
Subject: Re: [PATCH net-next v17 1/2] hinic3: Add ethtool statistic ops part1
Date: Wed, 21 Oct 2026 16:54:39 -0700 [thread overview]
Message-ID: <20261021165439.1a795e5d@kernel.org> (raw)
In-Reply-To: <20261021082104.14495-1-gongfan1@huawei.com>
On Wed, 21 Oct 2026 16:21:04 +0800 Fan Gong wrote:
> > On Thu, 15 Oct 2026 17:55:43 +0800 Fan Gong wrote:
> > > + HINIC3_RXQ_STAT(alloc_skb_err),
> > > + HINIC3_RXQ_STAT(alloc_rx_buf_err),
> >
> > Why bother separating these two? Rx packet was lost due to memory
> > pressure, doesn't matter which part failed to alloc.
>
> The `alloc_skb_err` counter signifies a failure in allocating a skb,
> whereas `alloc_rx_buf_err` indicates a failure in allocating the data
> buffer referenced by the skb. Given that these two resources are allocated
> and managed independently, distinct counters have been implemented for each.
Okay, so no good reason. Please use the standard alloc_fail stat
instead.
> > On Thu, 15 Oct 2026 17:55:43 +0800 Fan Gong wrote:
> > > + HINIC3_PORT_STAT(mac_rx_1519_max_bad_pkt_num),
> > > + HINIC3_PORT_STAT(mac_rx_1519_max_good_pkt_num),
> >
> > Isn't the 1519_max_good just the last RMON histogram bucket?
>
> The `mac_rx_1519_max_bad_pkt_num` metric functions as a specialized counter;
> strictly speaking, it is not the last RMON histogram bucket. It quantifies
> the aggregate number of packets exceeding 1,518 bytes while simultaneously
> providing granular statistics for such oversized frames. Consequently,
> this metric is classified as a private, non-standard counter within
> the `ethtool -S` output.
AFAIU user can just add up the buckets >=1519 ?
> > > +static struct hinic3_stats hinic3_tx_queue_stats[] = {
> > > + HINIC3_TXQ_STAT(gso_packets),
> >
> > Isn't this the standard lso/tso counter from queue stats?
>
> Yes, it is.
Remove it please.
next prev parent reply other threads:[~2026-10-21 23:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 3:45 [PATCH net-next v17 0/2] net: hinic3: Support ethtool ops Fan Gong
2026-10-19 3:45 ` [PATCH net-next v17 1/2] hinic3: Add ethtool statistic ops part1 Fan Gong
2026-10-21 0:51 ` Jakub Kicinski
2026-10-21 8:21 ` Fan Gong
2026-10-21 23:54 ` Jakub Kicinski [this message]
2026-10-22 3:46 ` netdev-bot+sashiko
2026-10-19 3:45 ` [PATCH net-next v17 2/2] hinic3: Add ethtool statistic ops part2 Fan Gong
2026-10-22 3:46 ` netdev-bot+sashiko
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=20261021165439.1a795e5d@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dimitri.daskalakis1@gmail.com \
--cc=edumazet@google.com \
--cc=gongfan1@huawei.com \
--cc=horms@kernel.org \
--cc=hramamurthy@google.com \
--cc=ioana.ciornei@nxp.com \
--cc=larysa.zaremba@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=mohsin.bashr@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tengpeisen@huawei.com \
--cc=vadim.fedorenko@linux.dev \
--cc=wudi234@huawei.com \
--cc=wulike1@huawei.com \
--cc=zhoushuai28@huawei.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