sst-elements icon indicating copy to clipboard operation
sst-elements copied to clipboard

StdMem for atomic memory operations without cache

Open mrutt92 opened this issue 1 year ago • 2 comments

Hi,

Is it possible to use the standardInterface in memHierarchy for atomic memory ops? I noticed the ReadLock and WriteUnlock commands in stdMem.h but they don't seem to guarantee exclusivity when I connected a standardInterface to a memoryController.

If I wanted to add this functionality without resorting to a cache, what would be the right way to do that?

mrutt92 avatar Jul 21 '23 18:07 mrutt92

Any ideas on this?

mrutt92 avatar Jul 25 '23 20:07 mrutt92

@mrutt92 memHierarchy implements the atomicity logic for ReadLock/WriteUnlock in the L1 caches only. If you wanted to add in that functionality, look at memHierarchy/memBackend/memBackendConvertor.cc::handleMemEvent() and the function it calls, memHierarchy/memBackend/membackendConvertor.h::setupMemReq(). This is where the logic for how and when the memory controller issues a request is implemented.

gvoskuilen avatar Aug 11 '23 16:08 gvoskuilen