junrushao1994 commented on a change in pull request #5:
URL: https://github.com/apache/tvm-rfcs/pull/5#discussion_r661745758
##########
File path: rfcs/0001-meta-schedule-autotensorir.md
##########
@@ -0,0 +1,297 @@
+* Feature Name: Meta Schedule (AutoTensorIR)
+* Start Date: 2021-05-28
+* RFC PR: TBD (apache/tvm-rfcs#0000)
+* GitHub Issue: TBD (apache/tvm-rfcs#0000)
+
+## 1. Summary
+
+This proposal introduces Meta Schedule: a probabilistic scheduling DSL on TIR
that unifies the approaches of AutoTVM and Auto Scheduler (Ansor). Meta
schedule provides a pragmatic way to define the space of automatic tuning,
extensibility in terms of all possible TIR schedule primitives like
tensorization and loop partitioning, and customizability on every layer of the
automation system.
+
+Meta Schedule is our 3rd generation automatic scheduling system.
+
+## 2. Motivation
+
+**Scheduling and Design Space**
+
+In TVM TensorIR, optimization of a TensorIR program is done via a sequence of
transformations. For example, we reorder loops for better locality and we
tensorize for specific hardware intrinsics. The process of invoking such a set
of pre-defined transformations is called “**scheduling**”, and each
transformation is called a “**schedule primitive**”. These primitives form a
domain-specific language (DSL) describing the transformation of TensorIR
programs. **Design space** is the set of all possible schedulings with respect
to a TensorIR program.
+
+**Problems with the Current Scheduling System**
+
+* **Manual schedule**: Developers optimize their programs by manually invoking
schedule primitives, i.e. explore points in the design space with humans in the
loop. This can be a tedious and error-prone approach, hence the creation of
AutoTVM and AutoScheduler (Ansor).
+* **AutoTVM**: The automation system requires users to define “schedule
templates” as the design space for each operator. Therefore, it is inextensible
to hundreds of operators.
+* **AutoScheduler (Ansor)**: It automatically generates schedule templates as
the design space, according to a set of predefined “search rules”. However, it
is non-trivial to extend AutoScheduler to new schedule primitives (tensorize,
loop partition, software pipelining).
Review comment:
added etc here
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscr...@tvm.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
