You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@shenjiangqiu Hi, recently I was also confused about this mapping, I wonder where you found the mapping scheme you proposed for ddr4 and HBM. All these mappings are black boxes?
In addition, I am very surprised that the "channel" is located in the low bit (e.g., RoBaBgRaCoCh). Does this mean that the addresses in a 4KB physical page will be assigned to different channels, that is, a 4KB physical page will store on different DDR DDIMs? Hereby ask for advice.
@shenjiangqiu Hi, recently I was also confused about this mapping, I wonder where you found the mapping scheme you proposed for ddr4 and HBM. All these mappings are black boxes?
In addition, I am very surprised that the "channel" is located in the low bit (e.g., RoBaBgRaCoCh). Does this mean that the addresses in a 4KB physical page will be assigned to different channels, that is, a 4KB physical page will store on different DDR DDIMs? Hereby ask for advice.
hi @joannahuadu , For HBM mapping scheme, you can find the code at src/HBM.cpp:12.
Yes, when Ch is at the lower bits, it assumes the BYTES are interleaved across the channels.
Furthermore, You can find my rewrite in rust: ramu_rs
in file
src/Memory.h
318-333the code implicates two mapping schemes for those Config with a bank group like ddr4 or HBM. (
Bg
for bank group)ChRaBaRoCo
assumesChRaBgBaRoCo
.RoBaRaCoCh
assumesRoBaBgRaCoCh
.( Should that beRoBgBaRaCoCh
for the correct design?)it that correct for the design?
If that is the case, I'll submit a pull request for it.
The text was updated successfully, but these errors were encountered: