perf (continuations): Remove the l2g MU selector#760
Draft
nicole-graus wants to merge 3 commits into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Instead of
MU = 0padding, the L2G table is padded with real "brought-forward" rows for untouched memory cells (value carried forward unchanged,fini_timestamp = 0). These are genuine no-ops: they self-cancel on the epoch-local Memory bus and telescope as value-preserving links on the GlobalMemory bus, so no selector is needed. With the column gone, every interaction fires with multiplicity 1.The prover draws fillers from each epoch's touched pages (genesis pages as a fallback) and fails closed if an epoch touches too large a fraction of memory.