At the mlir dev conference, I was chatting with our colleagues from ByteDance, and we thought it was time to get a workgroup together to land the PyTorch2 uplift that we talked about a couple of weeks ago in the context of Turbine.
I think we basically have all of the pieces needed now to complete Sean’s long term roadmap that he posted a year ago, and it is down to doing some project cleanup and landing.
I suggested that once the conference wraps, I could write a plan to reorganize the project, and then maybe we could get a weekly workgroup together to land the patches. I don’t think it would take very long if we work together and intentionally on it.
Having a pretty good view of the code, I think that this plan will aim to reorganize the project around an MLIR core with add-on components for:
- Pure Python libraries that can be included in your project to import and exercise lowerings.
- Utilities for interfacing to PyTorch to do code generation of op libraries and such.
- Native integrations with PyTorch that people are using (LTC, etc).
- New test suite that can validate a backend using more upstream friendly techniques.
- Original TorchScript tooling, APIs and test suite.
Basically, for those of us on the PT2 pure Python path, I’d like to organize the project so that is all we need while still meeting the needs of people who have integrated in a different way. For this subset, we just use the torch and related dialects directly as inputs to our compilers versus cutting between the projects at the current intermediate dialects.
Thoughts? I think this can be done in place if we plan it right but it will require some reorganization. This would also be a good time to drop components that don’t have current users.
Are there people who would like to participate in this uplift? I’m willing to do some of the earth moving but would like to have some collaborators on getting it done.
- Stella
26 posts - 9 participants