Hello, I'm interested in helping implement the forward convolution kernel, which is marked as 馃搮 Planned in ROADMAP.md.
After browsing through the repository, I've come up with a couple of questions/thoughts to shape the implementation direction
Design proposal:
- Following the existing convention that op signatures mirror PyTorch's, I plan on implementing separate variants, such as
conv1d, conv2d, etc., as opposed to one master conv op
- I think starting with conv1d first would be more effective. Perhaps I can create a draft PR so that I can receive feedback before expanding the scope for larger dimensions
- bf16/fp16 inputs with FP32 accumulation. FP32 inputs via TF32 on tensor cores to match
matmul.py
- NCHW layout
- Benchmark against
F.convNd (cuDNN)
Questions:
- Are there any internal blockers or overlapping work not yet reflected in the repository that I should be aware of?
- Is an NHCW eventually needed or is NCHW sufficient?
- I am currently using an RTX 5060 Ti, meaning that if I conduct performance profiling before making a PR, my numbers likely won't be as decisive compared to a B200 card. Is that ok?
Any additional tips/help/feedback would be much appreciated. Thank you! :D
Hello, I'm interested in helping implement the forward convolution kernel, which is marked as
馃搮 Plannedin ROADMAP.md.After browsing through the repository, I've come up with a couple of questions/thoughts to shape the implementation direction
Design proposal:
conv1d,conv2d, etc., as opposed to one masterconvopmatmul.pyF.convNd(cuDNN)Questions:
Any additional tips/help/feedback would be much appreciated. Thank you! :D