junrushao1994 commented on a change in pull request #5:
URL: https://github.com/apache/tvm-rfcs/pull/5#discussion_r676808880
##########
File path: rfcs/0001-meta-schedule-autotensorir.md
##########
@@ -64,8 +76,17 @@ primitives form a domain-specific language (DSL) describing
the transformation o
## 3. Guide-level explanation
-In this section, we describe the syntax of meta schedule DSL, and how it could
be used to describe
-and auto-generate the design space.
+Meta Schedule DSL is a flexible way to define or auto-generate the design
space.
+
+This section introduces its syntax of meta schedule DSL and usage in terms of
describing and
+auto-generating the design space, more specifically, its APIs for:
+1) Manually constructing a schedule using existing schedule primitives
(Section 3.1);
+2) Defining composite schedule to simplify the ap sequence of schedule
primitives (Section 3.2);
+3) Describing a design space of possible schedules,
+a.k.a. AutoTVM-style schedule templates (Section 3.3);
+4) Automatically generating the design space, a.k.a. Ansor-style search rules
(Section 3.4);
Review comment:
Yeah I agree that we should just converge to a single name, i.e.
AutoScheduler, given Ansor == AutoScheduler. I should put a citation somewhere
so that the readers could find the Ansor paper more easily
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
