-
Notifications
You must be signed in to change notification settings - Fork 14
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Support dram memory space in metal direct (#584)
This change adds support for the device dram memory space in metal backend. This required a few bits of refactoring including: - `DeviceAttr` splits out worker grid from L1 map, they now respectively map the physical compute cores and the physical L1 memory map. - `DeviceAttr` gets a new map, `dramMap`, which maps a linear tensor coordinate to a physical dram address. - Change `projectOnto` to take an arbitrary affine map instead of a grid attr. This let's us pass in unique affine map for L1 or DRAM or Eth (in the future) to the same interface. - `PhysicalCoreCoordMapping` can now take an L1 grid or a DRAM grid. - Giving explicit enum index names for the DeviceAttr affine map results. - Noc datamovement program can now be generated as reads or writes, necessary for writing to DRAM since dram cores do not have risc. Closes #359
- Loading branch information
Showing
12 changed files
with
518 additions
and
186 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.