From: Paul Fertser <fercerpav@gmail.com>
To: kalavakunta.hari.prasad@gmail.com
Cc: sam@mendozajonas.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
npeacock@meta.com, akozlov@meta.com, hkalavakunta@meta.com
Subject: Re: [PATCH net-next v3] net: ncsi: Fix GCPS 64-bit member variables
Date: Fri, 11 Apr 2025 14:22:57 +0300 [thread overview]
Message-ID: <Z/j7kdhvMTIt2jgt@home.paul.comp> (raw)
In-Reply-To: <20250410172247.1932-1-kalavakunta.hari.prasad@gmail.com>
Hello Hari,
On Thu, Apr 10, 2025 at 10:22:47AM -0700, kalavakunta.hari.prasad@gmail.com wrote:
> From: Hari Kalavakunta <kalavakunta.hari.prasad@gmail.com>
>
> Correct Get Controller Packet Statistics (GCPS) 64-bit wide member
> variables, as per DSP0222 v1.0.0 and forward specs. The Driver currently
> collects these stats, but they are yet to be exposed to the user.
> Therefore, no user impact.
>
> Statistics fixes:
> Total Bytes Received (byte range 28..35)
> Total Bytes Transmitted (byte range 36..43)
> Total Unicast Packets Received (byte range 44..51)
> Total Multicast Packets Received (byte range 52..59)
> Total Broadcast Packets Received (byte range 60..67)
> Total Unicast Packets Transmitted (byte range 68..75)
> Total Multicast Packets Transmitted (byte range 76..83)
> Total Broadcast Packets Transmitted (byte range 84..91)
> Valid Bytes Received (byte range 204..11)
>
> v2:
> - __be64 for all 64 bit GCPS counters
>
> v3:
> - be64_to_cpup() instead of be64_to_cpu()
Usually the changelog should go after --- so it's not included in the
final commit message when merged. I hope in this case the maintainers
will take care of this manually so no need to resend unless they ask
to.
Other than that,
Reviewed-by: Paul Fertser <fercerpav@gmail.com>
Thank you for working on this. I'll be looking forward to your next
patch where response validation is added.
BTW, have you already discussed how exactly you plan to expose the
statistics to the userspace, is that something that should end up
visible via e.g. `ethtool -S eth0 --groups nc-si` ?
next prev parent reply other threads:[~2025-04-11 11:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-10 17:22 [PATCH net-next v3] net: ncsi: Fix GCPS 64-bit member variables kalavakunta.hari.prasad
2025-04-11 11:22 ` Paul Fertser [this message]
2025-04-15 11:09 ` Paolo Abeni
2025-04-15 11:42 ` Paul Fertser
2025-04-15 17:41 ` Hari Kalavakunta
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=Z/j7kdhvMTIt2jgt@home.paul.comp \
--to=fercerpav@gmail.com \
--cc=akozlov@meta.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkalavakunta@meta.com \
--cc=horms@kernel.org \
--cc=kalavakunta.hari.prasad@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=npeacock@meta.com \
--cc=pabeni@redhat.com \
--cc=sam@mendozajonas.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