-
Notifications
You must be signed in to change notification settings - Fork 251
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
remove cu price rounding #3047
remove cu price rounding #3047
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall look reasonable, it is essentially a manual revert of solana-labs#31549.
I closed related feature Issue solana-labs#31453.
/// to be set by bank.feature_set.is_active(round_compute_unit_price::id()) at the moment | ||
/// the packet is built. | ||
/// This field can be removed when the above feature gate is adopted by mainnet-beta. | ||
const ROUND_COMPUTE_UNIT_PRICE = 0b0010_0000; | ||
/// For tracking performance | ||
const PERF_TRACK_PACKET = 0b0100_0000; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might be better to change it to 0010_000
, so there would be no "gap"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These are serialized in banking_trace data, so I think best to keep the meaning of each flag consistent.
ROUND_COMPUTE_UNIT_PRICE
is actually an exception since that was populated only in banking_stage's copy of the Packet
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still not great to leave a gap in bit flags. If don't want to introduce a break change in banking_trace at the moment, how about tag 0b0010_0000
as UNUSED
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
540ddc4
to
f9687a3
Compare
f9687a3
to
1378868
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Problem
Packet
insideBankingStage
which is bad for us moving to zero-copy approachSummary of Changes
Fixes #