On 2024/1/9 10:19, Jie Hai wrote:
On 2023/12/14 20:49, Ferruh Yigit wrote:
On 12/14/2023 1:56 AM, Jie Hai wrote:
The ethdev library now registers a telemetry command for
dump regs.
An example usage is shown below:
--> /ethdev/regs,test
{
"/ethdev/regs": {
"regs_offset": 0,
"regs_length": 3192,
"regs_width": 4,
"device_version": "0x1080f00",
"regs_file": "port_0_regs_test"
}
}
Above code writes register data to a file.
I am not sure about this kind of usage of telemetry command, that it
cause data to be written to a file.
My understanding is, telemetry usage is based on what telemetry client
receives.
What do you think just keep the 'reg_info' fields excluding data to the
file?
.Hi, Ferruh
I tried to write all register information to telemetry data,
but gave up because some drivers had too many registers (eg.ixgbe)
Sorry, correct it. It is i40e who has the most registers.
to carry. Therefore, the writing data to file approach is selected.
When we query a register, the register content is the key.
The information such as the width and length is only auxiliary
information. If the register data cannot be obtained, the auxiliary
information is optional. So I don't think register data should be removed.
In my opinion, writing a file is a more appropriate way to do it.
I wonder if there's a better way.
Best regards,
Thanks
