[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1d570fb8-1da0-4aa6-99f5-052adf559091@gmail.com>
Date: Tue, 8 Apr 2025 11:53:47 -0700
From: Hari Kalavakunta <kalavakunta.hari.prasad@...il.com>
To: Paul Fertser <fercerpav@...il.com>
Cc: Sam Mendoza-Jonas <sam@...dozajonas.com>, davem@...emloft.net,
edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com, horms@...nel.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org, npeacock@...a.com,
akozlov@...a.com
Subject: Re: [PATCH net-next 0/2] GCPS Spec Compliance Patch Set
On 4/8/2025 11:26 AM, Paul Fertser wrote:
> Can you please add the checks so that we are sure that hardware,
> software and the specification all match after your fixes?
Sure, I can give a try. Could you please provide an example or guideline
that I can use as a reference for proper alignment?
>
> Also, please do provide the example counter values read from real
> hardware (even if they're not yet exposed properly you can still
> obtain them with some hack; don't forget to mention what network card
> they were read from).
Our verification process is centered on confirming that the counter
values are accurately populated within the ncsi_channel_stats struct,
specifically in the ncsi_rsp_handler_gcps function. This verification is
conducted using synthesized statistics, rather than actual data from a
network card. Sure, I will provide NCSI packet capture showing the
synthesized data used for testing by end of the day.
Powered by blists - more mailing lists