memory tiering: calculate abstract distance based on ACPI HMAT
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v1 Latest posting 2/24 patches 36 repliesIn review
- v1 posting 1/24 patches 0 repliesSuperseded
Changes in v1 from the cover letter
- Added some comments per Aneesh's comments, Thanks!
Patches in v1 posting 2/2 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | memory tiering: add abstract distance calculation algorithms managementinclude/ mm/ | +78 | 17 replies | |
| 2/4 | acpi, hmat: refactor hmat_register_target_initiators()drivers/ | +30 | 3 replies | |
| 3/4 | acpi, hmat: calculate abstract distance with HMATdrivers/ include/ mm/ | +140 | 4 replies | |
| 4/4 | dax, kmem: calculate abstract distance with general interfacedrivers/ include/ mm/ | +44 | 7 replies |
Reviews trailers per patch
1 of 4 patches has a Reviewed-by or Acked-by.
| Patch | Alistair Popple |
|---|---|
| 1/4 | |
| 2/4 | R-b T-b |
| 3/4 | |
| 4/4 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH RESEND 0/4] memory tiering: calculate abstract distance based on ACPI HMAT
We have the explicit memory tiers framework to manage systems with multiple types of memory, e.g., DRAM in DIMM slots and CXL memory devices. Where, same kind of memory devices will be grouped into memory types, then put into memory tiers. To describe the performance of a memory type, abstract distance is defined. Which is in direct proportion to the memory latency and inversely proportional to the memory bandwidth. To keep the code as simple as possible, fixed abstract distance is used in dax/kmem to describe slow memory such as Optane DCPMM.
To support more memory types, in this series, we added the abstract distance calculation algorithm management mechanism, provided a algorithm implementation based on ACPI HMAT, and used the general abstract distance calculation interface in dax/kmem driver. So, dax/kmem can support HBM (high bandwidth memory) in addition to the original Optane DCPMM.
Changelog:
V1 (from RFC):
- Added some comments per Aneesh's comments, Thanks!
Best Regards,
Huang, Ying