-
Notifications
You must be signed in to change notification settings - Fork 4
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
use store_opts to vehicle offset and load/store data size for disk operations #27
Comments
tomcucinotta
changed the title
use store_opts to vehicle offset and data-size to load/store on disk
use store_opts to vehicle offset and load/store data size for disk operations
Aug 21, 2023
deRemo
added a commit
to deRemo/distwalk
that referenced
this issue
Sep 8, 2023
deRemo
added a commit
to deRemo/distwalk
that referenced
this issue
Sep 9, 2023
tomcucinotta
pushed a commit
that referenced
this issue
Sep 9, 2023
tomcucinotta
pushed a commit
that referenced
this issue
Sep 9, 2023
deRemo
added a commit
to deRemo/distwalk
that referenced
this issue
Sep 10, 2023
deRemo
added a commit
to deRemo/distwalk
that referenced
this issue
Sep 10, 2023
… (which has a weird accumulator behavior)(issue tomcucinotta#27 and tomcucinotta#21)
deRemo
added a commit
to deRemo/distwalk
that referenced
this issue
Sep 11, 2023
deRemo
added a commit
to deRemo/distwalk
that referenced
this issue
Sep 11, 2023
… (which has a weird accumulator behavior)(issue tomcucinotta#27 and tomcucinotta#21)
deRemo
added a commit
to deRemo/distwalk
that referenced
this issue
Sep 11, 2023
deRemo
added a commit
to deRemo/distwalk
that referenced
this issue
Sep 11, 2023
… (which has a weird accumulator behavior)(issue tomcucinotta#27 and tomcucinotta#21)
deRemo
added a commit
to deRemo/distwalk
that referenced
this issue
Sep 11, 2023
… (which has a weird accumulator behavior)(issue tomcucinotta#27 and tomcucinotta#21)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The store_opts (currently unused) structure might be useful to emulate sequential vs random data access patterns.
Also, it might be useful to tell the server what storage device to use, e.g., though a simple dev_id identifier (0, 1, 2, ...), to exploit multiple disk devices if available on the server, for emulating disk-related workloads taking advantage of multiple disks (e.g., data stores).
Related issue: #20
The text was updated successfully, but these errors were encountered: