junrushao1994 commented on a change in pull request #5: URL: https://github.com/apache/tvm-rfcs/pull/5#discussion_r676873020
########## File path: rfcs/0001-meta-schedule-autotensorir.md ########## @@ -107,29 +128,64 @@ best schedule according to measurement results on their device. As introduced in the previous section, in TensorIR, each schedule primitive handles only a very basic transformation of the IR. For example, `split` only splits a loop into two new loops. In the real world, the over-fine granularity of those primitives usually leads to repetitive and verbose -scheduling code, as -[mentioned](https://discuss.tvm.apache.org/t/rfc-tensorir-a-schedulable-ir-for-tvm/7872/43?u=junrushao1994) -by developers in our community. +scheduling code. Take the code snippet in the previous section as an example, a sequence of `split`s +are invoked, followed by a `reorder`, and all these together are called "SSRSRS" tiling. + +To make it more convenient and modular, users are allowed to register **composite schedules** that apply +a sequence of schedule primitives according to certain analysis of the IR. The word *composite* here +is used against the word *primitive*, which means it is a transformation *composed* of those Review comment: Thanks for helping me rephrase! It reads much better :-) -- 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]
