Skip to content

Decouple blob ids from recorded device addresses - #188

Open
cmelone wants to merge 2 commits into
developfrom
decouple-blob-id
Open

Decouple blob ids from recorded device addresses #188
cmelone wants to merge 2 commits into
developfrom
decouple-blob-id

Conversation

@cmelone

@cmelone cmelone commented Aug 29, 2026

Copy link
Copy Markdown
Collaborator

Mneme stores recorded device addresses as the IDs of blobs, snapshots, and replay pointer values.

Working on the subregion annotation feature, I was running into issues where the exact recorded VA base wasn't available. I think this could be ameliorated by storing blob_id along with an offset relative to the VA base, allowing us to manage regions within a blob and reduce dependence on the exact address.

Mneme stores recorded device addresses as the IDs of blobs, snapshots, and replay pointer values.

Working on the subregion annotation feature, I was running into issues where the exact recorded VA base wasn't available. I think this could be ameliorated by storing blob_id along with an offset relative to the VA base, allowing us to manage regions within a blob and reduce dependence on the exact address.

Signed-off-by: Caetano Melone <melone1@llnl.gov>
Signed-off-by: Caetano Melone <melone1@llnl.gov>
@cmelone

cmelone commented Aug 29, 2026

Copy link
Copy Markdown
Collaborator Author

@ZwFink came across some issues as I was working on your #187 review..sorry if this steps over #164 😔

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant