[Inductor cutlass backend] Experimental extended Cutlass op generator #113932
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
So far we have relied on the "generator.py" from third_party/cutlass/python/cutlass_library/ to generate Cutlass op configurations to be tried in autotuning. These op configs are not sufficient to ensure good performance and dtype coverage in all cases. This diff introduces an extended variant of that generator.py, provided both as a source file and as a diff ( so that it may be applied to future versions of cutlass_library.generator ) Test Plan: * CI * python test/inductor/test_max_autotune.py [ghstack-poisoned]
This was referenced Nov 17, 2023
This was referenced Nov 17, 2023
…p generator" So far we have relied on the "generator.py" from third_party/cutlass/python/cutlass_library/ to generate Cutlass op configurations to be tried in autotuning. These op configs are not sufficient to ensure good performance and dtype coverage in all cases. This diff introduces an extended variant of that generator.py, provided both as a source file and as a diff ( so that it may be applied to future versions of cutlass_library.generator ) Test Plan: * CI * python test/inductor/test_max_autotune.py [ghstack-poisoned]
…p generator" So far we have relied on the "generator.py" from third_party/cutlass/python/cutlass_library/ to generate Cutlass op configurations to be tried in autotuning. These op configs are not sufficient to ensure good performance and dtype coverage in all cases. This diff introduces an extended variant of that generator.py, provided both as a source file and as a diff ( so that it may be applied to future versions of cutlass_library.generator ) Test Plan: * CI * python test/inductor/test_max_autotune.py [ghstack-poisoned]
…p generator" So far we have relied on the "generator.py" from third_party/cutlass/python/cutlass_library/ to generate Cutlass op configurations to be tried in autotuning. These op configs are not sufficient to ensure good performance and dtype coverage in all cases. This diff introduces an extended variant of that generator.py, provided both as a source file and as a diff ( so that it may be applied to future versions of cutlass_library.generator ) Test Plan: * CI * python test/inductor/test_max_autotune.py [ghstack-poisoned]
kadeng
added a commit
that referenced
this pull request
Nov 17, 2023
So far we have relied on the "generator.py" from third_party/cutlass/python/cutlass_library/ to generate Cutlass op configurations to be tried in autotuning. These op configs are not sufficient to ensure good performance and dtype coverage in all cases. This diff introduces an extended variant of that generator.py, provided both as a source file and as a diff ( so that it may be applied to future versions of cutlass_library.generator ) Test Plan: * CI * python test/inductor/test_max_autotune.py ghstack-source-id: b7fba12c9ec00defefeb1c4a29fd1005478fe03a Pull Request resolved: #113932
…p generator" So far we have relied on the "generator.py" from third_party/cutlass/python/cutlass_library/ to generate Cutlass op configurations to be tried in autotuning. These op configs are not sufficient to ensure good performance and dtype coverage in all cases. This diff introduces an extended variant of that generator.py, provided both as a source file and as a diff ( so that it may be applied to future versions of cutlass_library.generator ) Test Plan: * CI * python test/inductor/test_max_autotune.py [ghstack-poisoned]
…p generator" So far we have relied on the "generator.py" from third_party/cutlass/python/cutlass_library/ to generate Cutlass op configurations to be tried in autotuning. These op configs are not sufficient to ensure good performance and dtype coverage in all cases. This diff introduces an extended variant of that generator.py, provided both as a source file and as a diff ( so that it may be applied to future versions of cutlass_library.generator ) Test Plan: * CI * python test/inductor/test_max_autotune.py [ghstack-poisoned]
…p generator" So far we have relied on the "generator.py" from third_party/cutlass/python/cutlass_library/ to generate Cutlass op configurations to be tried in autotuning. These op configs are not sufficient to ensure good performance and dtype coverage in all cases. This diff introduces an extended variant of that generator.py, provided both as a source file and as a diff ( so that it may be applied to future versions of cutlass_library.generator ) Test Plan: * CI * python test/inductor/test_max_autotune.py [ghstack-poisoned]
This was referenced Nov 21, 2023
Closed
…p generator" So far we have relied on the "generator.py" from third_party/cutlass/python/cutlass_library/ to generate Cutlass op configurations to be tried in autotuning. These op configs are not sufficient to ensure good performance and dtype coverage in all cases. This diff introduces an extended variant of that generator.py, provided both as a source file and as a diff ( so that it may be applied to future versions of cutlass_library.generator ) Test Plan: * CI * python test/inductor/test_max_autotune.py [ghstack-poisoned]
This was referenced Dec 5, 2023
…p generator" So far we have relied on the "generator.py" from third_party/cutlass/python/cutlass_library/ to generate Cutlass op configurations to be tried in autotuning. These op configs are not sufficient to ensure good performance and dtype coverage in all cases. This diff introduces an extended variant of that generator.py, provided both as a source file and as a diff ( so that it may be applied to future versions of cutlass_library.generator ) Test Plan: * CI * python test/inductor/test_max_autotune.py [ghstack-poisoned]
…p generator" So far we have relied on the "generator.py" from third_party/cutlass/python/cutlass_library/ to generate Cutlass op configurations to be tried in autotuning. These op configs are not sufficient to ensure good performance and dtype coverage in all cases. This diff introduces an extended variant of that generator.py, provided both as a source file and as a diff ( so that it may be applied to future versions of cutlass_library.generator ) Test Plan: * CI * python test/inductor/test_max_autotune.py [ghstack-poisoned]
…p generator" So far we have relied on the "generator.py" from third_party/cutlass/python/cutlass_library/ to generate Cutlass op configurations to be tried in autotuning. These op configs are not sufficient to ensure good performance and dtype coverage in all cases. This diff introduces an extended variant of that generator.py, provided both as a source file and as a diff ( so that it may be applied to future versions of cutlass_library.generator ) Test Plan: * CI * python test/inductor/test_max_autotune.py [ghstack-poisoned]
…p generator" So far we have relied on the "generator.py" from third_party/cutlass/python/cutlass_library/ to generate Cutlass op configurations to be tried in autotuning. These op configs are not sufficient to ensure good performance and dtype coverage in all cases. This diff introduces an extended variant of that generator.py, provided both as a source file and as a diff ( so that it may be applied to future versions of cutlass_library.generator ) Test Plan: * CI * python test/inductor/test_max_autotune.py [ghstack-poisoned]
…p generator" So far we have relied on the "generator.py" from third_party/cutlass/python/cutlass_library/ to generate Cutlass op configurations to be tried in autotuning. These op configs are not sufficient to ensure good performance and dtype coverage in all cases. This diff introduces an extended variant of that generator.py, provided both as a source file and as a diff ( so that it may be applied to future versions of cutlass_library.generator ) Test Plan: * CI * python test/inductor/test_max_autotune.py [ghstack-poisoned]
…p generator" So far we have relied on the "generator.py" from third_party/cutlass/python/cutlass_library/ to generate Cutlass op configurations to be tried in autotuning. These op configs are not sufficient to ensure good performance and dtype coverage in all cases. This diff introduces an extended variant of that generator.py, provided both as a source file and as a diff ( so that it may be applied to future versions of cutlass_library.generator ) Test Plan: * CI * python test/inductor/test_max_autotune.py [ghstack-poisoned]
…p generator" So far we have relied on the "generator.py" from third_party/cutlass/python/cutlass_library/ to generate Cutlass op configurations to be tried in autotuning. These op configs are not sufficient to ensure good performance and dtype coverage in all cases. This diff introduces an extended variant of that generator.py, provided both as a source file and as a diff ( so that it may be applied to future versions of cutlass_library.generator ) Test Plan: * CI * python test/inductor/test_max_autotune.py [ghstack-poisoned]
…p generator" So far we have relied on the "generator.py" from third_party/cutlass/python/cutlass_library/ to generate Cutlass op configurations to be tried in autotuning. These op configs are not sufficient to ensure good performance and dtype coverage in all cases. This diff introduces an extended variant of that generator.py, provided both as a source file and as a diff ( so that it may be applied to future versions of cutlass_library.generator ) Test Plan: * CI * python test/inductor/test_max_autotune.py [ghstack-poisoned]
…p generator" So far we have relied on the "generator.py" from third_party/cutlass/python/cutlass_library/ to generate Cutlass op configurations to be tried in autotuning. These op configs are not sufficient to ensure good performance and dtype coverage in all cases. This diff introduces an extended variant of that generator.py, provided both as a source file and as a diff ( so that it may be applied to future versions of cutlass_library.generator ) Test Plan: * CI * python test/inductor/test_max_autotune.py [ghstack-poisoned]
…p generator" So far we have relied on the "generator.py" from third_party/cutlass/python/cutlass_library/ to generate Cutlass op configurations to be tried in autotuning. These op configs are not sufficient to ensure good performance and dtype coverage in all cases. This diff introduces an extended variant of that generator.py, provided both as a source file and as a diff ( so that it may be applied to future versions of cutlass_library.generator ) Test Plan: * CI * python test/inductor/test_max_autotune.py [ghstack-poisoned]
…p generator" So far we have relied on the "generator.py" from third_party/cutlass/python/cutlass_library/ to generate Cutlass op configurations to be tried in autotuning. These op configs are not sufficient to ensure good performance and dtype coverage in all cases. This diff introduces an extended variant of that generator.py, provided both as a source file and as a diff ( so that it may be applied to future versions of cutlass_library.generator ) Test Plan: * CI * python test/inductor/test_max_autotune.py [ghstack-poisoned]
…p generator" So far we have relied on the "generator.py" from third_party/cutlass/python/cutlass_library/ to generate Cutlass op configurations to be tried in autotuning. These op configs are not sufficient to ensure good performance and dtype coverage in all cases. This diff introduces an extended variant of that generator.py, provided both as a source file and as a diff ( so that it may be applied to future versions of cutlass_library.generator ) Test Plan: * CI * python test/inductor/test_max_autotune.py [ghstack-poisoned]
This was referenced Dec 12, 2023
Closed
…p generator" So far we have relied on the "generator.py" from third_party/cutlass/python/cutlass_library/ to generate Cutlass op configurations to be tried in autotuning. These op configs are not sufficient to ensure good performance and dtype coverage in all cases. This diff introduces an extended variant of that generator.py, provided both as a source file and as a diff ( so that it may be applied to future versions of cutlass_library.generator ) Test Plan: * CI * python test/inductor/test_max_autotune.py [ghstack-poisoned]
|
Moved to a (draft) feature branch, see #115919 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Stack from ghstack (oldest at bottom):
So far we have relied on the "generator.py" from
third_party/cutlass/python/cutlass_library/ to generate Cutlass op
configurations to be tried in autotuning. These op configs are not
sufficient to ensure good performance and dtype coverage in all cases.
This diff introduces an extended variant of that generator.py,
provided both as a source file and as a diff ( so that it may be applied
to future versions of cutlass_library.generator )
Test Plan: