junrushao1994 commented on a change in pull request #5:
URL: https://github.com/apache/tvm-rfcs/pull/5#discussion_r676875856
##########
File path: rfcs/0001-meta-schedule-autotensorir.md
##########
@@ -147,17 +203,20 @@ sch.reorder(
### 3.4. AutoScheduler-style Design Space Generation
-AutoScheduler (Ansor) generates schedule templates by applying their
SearchRules to each stage.
-SearchRule analyzes TE and eagerly trigger schedule primitives accordingly in
its internally
-maintained mini IR.
+To generate design space, AutoScheduler (Ansor) applies a set of rules to each
TE stage.
+The rules analyze the TE operations and apply an internal DSL to manipulating
its internal IR,
+which is in the end mapped to TE schedule primitives. This process is called
*sketch generation*.
-As introduced in Section 3.2, composite schedule rules are equivalent to
AutoScheduler's SearchRule
-in TensorIR scheduling. To further generate a design space for scheduling,
sampling instructions are
-used in composite schedule rules. Similarly, the sketch generation phase in
AutoScheduler is
-equivalent to applying composite schedule rules to each block in TensorIR.
+Composite schedule rules work in a similar way scheduling TensorIR, as
introduced in Section 3.2.
+It analyzes the TensorIR and apply schedule primitives directly to TensorIR
accordingly.
+When applying such rules to each TensorIR block in certain order (e.g.
Post-DFS Order),
Review comment:
It is rare but possible that developers write their own order, but I
didn't see any meaningful usecases to change order though. So in other words,
we probably can post-DFS order is a provided builtin, but allows further
extension
--
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]
