[NestedLayout] Make layout use strides instead of basis (#17284)

This patch makes the layout store how threads and subgroups are
distributed as "strides" instead of basis.

Strides are just a mapping from `virtual tid --> tid` (where tid is
thread id). The mapping is a dot product between `virtual tid` and
`strides`:

```
tid = vtid * stride
```

If we put some restrictions on `strides` and make the mapping can be
made invertible with the inverse mapping:

```
vtid_i = tid floordiv stride_i mod size_i
```

The advantage with strides is that strides are only dependent on the
dimension they are working on, while basis actually depend on the order
of dimension because to get the distribution for dimension `i`, you need
to know the distribution for dimensions `i-1`. (If you think about it,
this is just skewing to remove dependency of`i` on `i-1`).

With strides, dimensions are essentially independent, and we do not need
any orders in the layout, which hugely simplifies the layout. This is
much closer to what CuTe layouts do (somewhat).

Along with this change, distribution now actually uses 2 new ops to
query the `tid -> virtual tid` map, which makes distribution independent
of these changes.

The reason for implementing this was that with strides, the layouts
actually have a canonical form, unlike with basis, because different
active ids, order, basis permutations can represent the same layout.
Having a canonical form helps a lot when try to match two different
matmul anchors.
15 files changed
tree: 222da9ed55a9214120a3626a8b98bb118165d203
  1. .devcontainer/
  2. .github/
  3. build_tools/
  4. compiler/
  5. docs/
  6. experimental/
  7. integrations/
  8. lib/
  9. llvm-external-projects/
  10. runtime/
  11. samples/
  12. tests/
  13. third_party/
  14. tools/
  15. .bazel_to_cmake.cfg.py
  16. .bazelignore
  17. .bazelrc
  18. .bazelversion
  19. .clang-format
  20. .dockerignore
  21. .git-blame-ignore-revs
  22. .gitattributes
  23. .gitignore
  24. .gitmodules
  25. .pre-commit-config.yaml
  26. .yamllint.yml
  27. AUTHORS
  28. BUILD.bazel
  29. CITATION.cff
  30. CMakeLists.txt
  31. configure_bazel.py
  32. CONTRIBUTING.md
  33. LICENSE
  34. MAINTAINERS.md
  35. README.md
  36. RELEASING.md
  37. WORKSPACE
README.md

IREE: Intermediate Representation Execution Environment

IREE (Intermediate Representation Execution Environment, pronounced as “eerie”) is an MLIR-based end-to-end compiler and runtime that lowers Machine Learning (ML) models to a unified IR that scales up to meet the needs of the datacenter and down to satisfy the constraints and special considerations of mobile and edge deployments.

See our website for project details, user guides, and instructions on building from source.

CI Status IREE Discord Status

Project Status

IREE is still in its early phase. We have settled down on the overarching infrastructure and are actively improving various software components as well as project logistics. It is still quite far from ready for everyday use and is made available without any support at the moment. With that said, we welcome any kind of feedback on any communication channels!

Communication Channels

Related Project Channels

  • MLIR topic within LLVM Discourse: IREE is enabled by and heavily relies on MLIR. IREE sometimes is referred to in certain MLIR discussions. Useful if you are also interested in MLIR evolution.

Architecture Overview

IREE Architecture IREE Architecture

See our website for more information.

Presentations and Talks

Community meeting recordings: IREE YouTube channel

  • 2021-06-09: IREE Runtime Design Tech Talk (recording and slides)
  • 2020-08-20: IREE CodeGen: MLIR Open Design Meeting Presentation (recording and slides)
  • 2020-03-18: Interactive HAL IR Walkthrough (recording)
  • 2020-01-31: End-to-end MLIR Workflow in IREE: MLIR Open Design Meeting Presentation (recording and slides)

License

IREE is licensed under the terms of the Apache 2.0 License with LLVM Exceptions. See LICENSE for more information.