8000 [feature request] [discussion] Include basic `ctypes` bindings for `cudart`/`cublasLt`/`cublas`/`nvrtc`/`cudnn` with stock PyTorch · Issue #107800 · pytorch/pytorch · GitHub
[go: up one dir, main page]

Skip to content
[feature request] [discussion] Include basic ctypes bindings for cudart/cublasLt/cublas/nvrtc/cudnn with stock PyTorch #107800
@vadimkantorov

Description

@vadimkantorov

🚀 The feature, motivation and pitch

This would make it more approachable experimenting with some new function variants (like quantized int8 gemms) earlier.

Example of such ctypes bindings: https://github.com/OpenBMB/cpm_kernels/tree/master/cpm_kernels/library
Including in core some bindings like this would be great! (maybe under some torch.cuda.ctypes.cublasLt or something similar)

Examples of such C bindings: https://github.com/TimDettmers/bitsandbytes/blob/18e827d666fa2b70a12d539ccedc17aa51b2c97c/csrc/ops.cu#L434

Another set of bindings is now in bitsandbytes, but having it directly available in Python would make it more approachable for experimentation and benchmarking

There might be problems with versions, but maybe then some bindings could be versioned as well: torch.cuda.ctypes.cublatltV8 or sth like that, so that the user is responsible for using the correct bindings for their experiments

Alternatives

No response

Additional context

No response

cc @ptrblck @csarofeen @xwang233

Metadata

Metadata

Assignees

No one assigned

    Labels

    featureA request for a proper, new feature.module: cublasProblem related to cublas supportmodule: cudaRelated to torch.cuda, and CUDA support in generaltriagedThis issue has been looked at a team member, and triaged and prioritized into an appropriate module

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0