timing(L1PrefetchComponent): defer sent_vec updates to pf fire#6102
Open
zzQGyy wants to merge 1 commit into
Open
timing(L1PrefetchComponent): defer sent_vec updates to pf fire#6102zzQGyy wants to merge 1 commit into
zzQGyy wants to merge 1 commit into
Conversation
github-actions
Bot
added
the
module: memory
Emu - Performance SummaryMetadata
IPC Report
|
ywlcode
approved these changes
Jun 24, 2026
Register the selected prefetch candidate metadata at the s1 boundary and use s1 valid signals to forward pending sent_vec updates during new candidate generation. Update the persistent sent_vec state only when the corresponding s1 prefetch request fires. This keeps downstream ready out of the s0 prefetch candidate path while still preventing duplicated requests from the in-flight s1 entry. This touches the L1, L2, and L3 prefetch issue paths in L1PrefetchComponent. The L2/L3 s1 valid signals are declared with the shared s1 metadata and assigned in their send stages to keep the pipeline boundary explicit. timing(L1PrefetchComponent): defer sent_vec updates to pf fire Register the selected prefetch candidate metadata at the s1 boundary and use s1 valid signals to forward pending sent_vec updates during new candidate generation. Update the persistent sent_vec state only when the corresponding s1 prefetch request fires. This keeps downstream ready out of the s0 prefetch candidate path while still preventing duplicated requests from the in-flight s1 entry. This touches the L1, L2, and L3 prefetch issue paths in L1PrefetchComponent. The L2/L3 s1 valid signals are declared with the shared s1 metadata and assigned in their send stages to keep the pipeline boundary explicit.
zzQGyy
force-pushed
the
kunminghu-v3-timing-l1_sent_vecV2
branch
from
b5118f0 to
f4751f3
Compare
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
2 participants
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.
Register the selected prefetch candidate metadata at the s1 boundary
and use s1 valid signals to forward pending sent_vec updates during
new candidate generation.
Update the persistent sent_vec state only when the corresponding s1
prefetch request fires. This keeps downstream ready out of the s0
prefetch candidate path while still preventing duplicated requests
from the in-flight s1 entry.
This touches the L1, L2, and L3 prefetch issue paths in
L1PrefetchComponent. The L2/L3 s1 valid signals are declared with the
shared s1 metadata and assigned in their send stages to keep the
pipeline boundary explicit.