nvml's `nvmlProcessInfo_t` `struct` uses the wrong type for `pid`

[SamuelMarks]

https://docs.nvidia.com/deploy/nvml-api/structnvmlProcessInfo__t.html#structnvmlProcessInfo__t_107c2ccda774b8bee86e68c3d3962533c

The type should be pid_t, e.g., see:

• Linux: https://man7.org/linux/man-pages/man2/getpid.2.html https://linux.die.net/man/2/getpid
• POSIX: https://pubs.opengroup.org/onlinepubs/009696699/functions/getpid.html
• zOS: https://www.ibm.com/docs/en/zos/2.4.0?topic=functions-getpid-get-process-id
• FreeBSD: https://man.freebsd.org/cgi/man.cgi?query=getpid&sektion=2

Some popular libc documentation:

• https://www.gnu.org/software/libc/manual/html_node/Process-Identification.html "The pid_t data type is a signed integer type which is capable of representing a process ID. In the GNU library, this is an int."
• https://github.com/llvm/llvm-project/blob/4f1474d/libc/include/llvm-libc-types/pid_t.h typedef __INT32_TYPE__ pid_t;
• http://git.musl-libc.org/cgit/musl/tree/include/alltypes.h.in TYPEDEF int pid_t;

Can you get the NVIDIA folk to change the type to match PIDs on all platforms? - As unsigned int seems to never be the right option.

[elezar]

@SamuelMarks this repo contains the golang bindings for NVML and we are as such only consumers of the header files. I will see if I can find out where this query / report can be directed.

[github-actions]

This issue is stale because it has been open 90 days with no activity. This issue will be closed in 30 days unless new comments are made or the stale label is removed. To skip these checks, apply the "lifecycle/frozen" label.

[SamuelMarks]

new comment; we should use the right types here

[github-actions]

This issue is stale because it has been open 90 days with no activity. This issue will be closed in 30 days unless new comments are made or the stale label is removed. To skip these checks, apply the "lifecycle/frozen" label.