From: Jakub Kicinski <kuba@kernel.org>
To: Akhilesh Samineni <akhilesh.samineni@broadcom.com>
Cc: Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
andrew+netdev@lunn.ch, horms@kernel.org, willemb@google.com,
daniel.zahka@gmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
jayakrishnan.udayavarma@broadcom.com, ajit.khaparde@broadcom.com,
kiran.kella@broadcom.com, sachin.suman@broadcom.com
Subject: Re: [net-next 1/3] psp: Support resetting statistics on a device
Date: Fri, 6 Mar 2026 12:34:16 -0800 [thread overview]
Message-ID: <20260306123416.33cc12e5@kernel.org> (raw)
In-Reply-To: <CANQF7iCc_t43FHa+fysnZ=vB9DibvkV5n7v10OXkbZ-Ogsyt2Q@mail.gmail.com>
On Fri, 6 Mar 2026 21:24:01 +0530 Akhilesh Samineni wrote:
> That said, if the common practice in netdev is to avoid providing
> explicit reset functionality for such statistics, we are fine with
> aligning with that convention and not introducing a deviation.
We generally support resetting the whole device or its specific
"blocks". Can't think of any reset specifically for stats.
next prev parent reply other threads:[~2026-03-06 20:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 19:53 [net-next 0/3] psp: Support PSP reset statistics Akhilesh Samineni
2026-03-02 19:53 ` [net-next 1/3] psp: Support resetting statistics on a device Akhilesh Samineni
2026-03-02 21:15 ` Willem de Bruijn
2026-03-05 10:54 ` Akhilesh Samineni
2026-03-05 14:25 ` Willem de Bruijn
2026-03-06 15:50 ` Akhilesh Samineni
2026-03-06 20:37 ` Willem de Bruijn
2026-03-05 14:59 ` Jakub Kicinski
2026-03-06 15:54 ` Akhilesh Samineni
2026-03-06 20:34 ` Jakub Kicinski [this message]
2026-03-02 19:53 ` [net-next 2/3] netdevsim: psp: Handle statistics reset Akhilesh Samineni
2026-03-02 19:53 ` [net-next 3/3] selftests: drv-net: psp: add reset statistics test Akhilesh Samineni
2026-03-02 23:05 ` Jakub Kicinski
2026-03-05 10:55 ` Akhilesh Samineni
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=20260306123416.33cc12e5@kernel.org \
--to=kuba@kernel.org \
--cc=ajit.khaparde@broadcom.com \
--cc=akhilesh.samineni@broadcom.com \
--cc=andrew+netdev@lunn.ch \
--cc=daniel.zahka@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jayakrishnan.udayavarma@broadcom.com \
--cc=kiran.kella@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sachin.suman@broadcom.com \
--cc=willemb@google.com \
--cc=willemdebruijn.kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.