Hi Thomas,

[...]

quoted

quoted

I am still unsure exactly what the use case is here - why are we
choosing to publish the pointer values through telemetry rather than
using a debug log for example?

Pointer values are useful sometimes for more debugging through telemetry,

hence this proposal.

quoted

As I mentioned in v1 thread, this is architecture compliant approach
rather than assuming pointer value is always 64 bit, when there is need to use

pointer value in current telemetry path.

Why using telemetry for debugging?
I agree with Ciara, debug log is more appropriate.
You can also use the tracing framework.

In addition to getting status/stats, we are using this library for remote debugging as this is the only mechanism available in DPDK now. For an instance, accessing data from a pointer address through a root privileged tool. We can internally type cast them to u64 as well but thought of standardizing the conversion through library API instead in case it is useful in other platforms too.

If it does not seem more useful for now, I will take another approach on type casting the values internally in our driver (and avoiding library patch). Please share your thoughts.

Thanks,
Gowrishankar