Skip to content

[Refactor] Meta Schedule RFC #21

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.

Sign up for GitHub

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

Merged
tqchen merged 2 commits into from
Aug 17, 2021
Merged

[Refactor] Meta Schedule RFC #21

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
cd9d0eb
Re-number the Meta Schedule RFC
junrushao Aug 15, 2021
15d07cb
update with Andrew's suggestions
junrushao Aug 15, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 12 additions & 8 deletions rfcs/0001-meta-schedule-autotensorir.md → rfcs/0005-meta-schedule-autotensorir.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,14 +31,18 @@ Meta Schedule is the 3rd generation automatic scheduling system.

## 2. Motivation

**Scheduling.** In TVM,
both TensorIR and TE allow direct or indirect IR transformation guided by a
developer-provided program, for example,
specifying a particular reordering of loops for better locality,
or tensorizing a compute region with specific hardware intrinsics.
The process of invoking such a set of pre-defined transformations is called "**scheduling**",
and each of such transformations is called a "**schedule primitive**".
These primitives form a domain-specific language (DSL).
**Scheduling.**
In TVM, computation of each operator is described
by either Tensor Expression (TE, the prior standard) or
[TensorIR](https://discuss.tvm.apache.org/t/rfc-tensorir-a-schedulable-ir-for-tvm/7872) (TIR).
Through a process known as **scheduling**,
TVM allows a pre-defined set of transformations over these IRs,
either lazily (transforms by manipulating the schedule tree)
or eagerly (transforms by manipulating TIR),
so that the end IRs could be lowered to code with potentially better performance.
Such transformations are guided by a developer-provided program,
which consist of this pre-defined set of transformations,
called **schedule primitives**.

**Design space.** The set of all possible schedulings of a TE/TensorIR is called its design space.
Optimization in TVM is essentially exploring such space to find out a scheduling that transforms the
Expand Down