Build wheels for pylibwholegraph

[tingyu66]

No description provided.

[vyasr]

Would recommend holding off on this until rapidsai/shared-workflows#116 is merged so that you can use the new workflows for wheels.

Separate question regarding the driver API usage, what APIs does wholegraph use and how new are they? Because if wholegraph requires a fairly new libcuda.so it's worth noting that the UX for installing the wheel into an environment with an older driver will be quite bad since there's really no way for us to constrain that. I imagine it'll fail to load the library correctly at runtime.

[tingyu66]

Would recommend holding off on this until rapidsai/shared-action-workflows#116 is merged so that you can use the new workflows for wheels.

Thanks. I have migrated the script based on the new wheel build workflow. I have excluded the driver library from auditwheel repair and wheel build and the test has passed in CI.

Separate question regarding the driver API usage, what APIs does wholegraph use and how new are they? Because if wholegraph requires a fairly new libcuda.so it's worth noting that the UX for installing the wheel into an environment with an older driver will be quite bad since there's really no way for us to constrain that. Assuming that it's linked to a particular SOVERSION it also won't be able to leverage anything except the same driver version it was built with.

I am probably not the best person to answer this, as @dongxuy04 is the main developer. But to my knowledge, the memory management functions used here are not new in the drivers API.

[dongxuy04]

Would recommend holding off on this until rapidsai/shared-action-workflows#116 is merged so that you can use the new workflows for wheels.

Thanks. I have migrated the script based on the new wheel build workflow. I have excluded the driver library from auditwheel repair and wheel build and the test has passed in CI.

Separate question regarding the driver API usage, what APIs does wholegraph use and how new are they? Because if wholegraph requires a fairly new libcuda.so it's worth noting that the UX for installing the wheel into an environment with an older driver will be quite bad since there's really no way for us to constrain that. Assuming that it's linked to a particular SOVERSION it also won't be able to leverage anything except the same driver version it was built with.

I am probably not the best person to answer this, as @dongxuy04 is the main developer. But to my knowledge, the memory management functions used here are not new in the drivers API.

@vyasr the Driver APIs used by wholegraph are virtual memory management APIs, like cuMemCreate, cuMemMap, cuMemAddressReserve, cuMemSetAccess, cuMemUnmap, cuMemRelease, cuMemAddressFree, and also IPC APIs like cuMemExportToShareableHandle, cuMemImportFromShareableHandle. I think they are supported from CUDA 11.0.

[BradReesWork]

/merge