-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RFC] Support Codegen Using Texture Memory #2250
Comments
I would recommend us to start with backend support for texture and list them as a separate device type. Once we have enough evidence to support the texture code, then we can start this migration |
@dmlc/tvm-comitter Just FYI there is other effort on this topic: https://medium.com/tensorflow/tensorflow-lite-now-faster-with-mobile-gpus-developer-preview-e15797e6dee7 I want to check whether there is other people in community plan to work on this problem so we may avoid redundant work. |
This should be supported now. |
Technically it hasn't been merged in but it's worth pointing to the RFCs and PRs for posterity @masahi: See this RFC to understand the broader contributions of the texture enablement work. There are several PRs that need to land in order for the texture support to be fully enabled in Open Source TVM. Some of these PRs will need to be revisited extensively before they can be merged, for instance in light of the work on TECompiler refactor, and efforts to provide physical and logical layout separation.
|
Thanks @tmoreau89, I've opened a fresh tracking #9891 |
Good idea, thank you @masahi ! |
Current TVM is not supporting mixture texture and buffer. This pattern is essential to obtain state-of-art performance on iOS device, and potentially better OpenGL backend for legacy devices.
A potential solution is providing extra device hints, eg:
In lowering process, some extra work is required I think:
Once we support 2D texture, I think we are able to achieve state-of-art performance on iOS, and OpenGL.
The text was updated successfully, but these errors were encountered: