-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GenericDRAMController seems does not support write transaction #30
Comments
Hi, Thanks for spotting this. Ramulator 2.0 does support writes in the DRAM model. The reason for this is that the This will cause issues if the user is using another frontend (e.g., in your case, your own frontend) that do needs write callbacks. We will modify the controller code to account for this, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I tried to use ramulator2 to test DDR write performance. A simple code is shown above:
A simple YAML file is shown above:
If I specify the
type
to1
, the request type isRamulator::Request::Type::Write
. I will never get a request callback.My running result:
After investigating the code, I found that the GenericDRAMController does not support write transactions and leaves the TODO in the code generic_dram_controller.cpp#L123.
If I copy the two lines of code from the read transaction processing to the write transaction processing and then recompile the ramultor2, I will get the callback from the write transaction but use the read latency for write transactions.
Is it my fault for misusing the ramulator2, or is the write transaction not supported now?
The text was updated successfully, but these errors were encountered: