Add experimental RouteSegmentedConnPool (OFFLOCK) #559
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
ok2c
approved these changes
Oct 4, 2025
Member
ok2c
left a comment
ok2c
left a comment
There was a problem hiding this comment.
@arturobernalg Same deal as with the H2 priority support. This implementation is your area of responsibility entirely. I only get involved if it spills into the public API or affects the critical execution path.
Looks good to me.
…oute-segmented, disposal off critical path; preserves STRICT/LAX semantics.
arturobernalg
force-pushed
the
offlock-pool
branch
from
f504699 to
4e0e2be
Compare
Member
|
@arturobernalg Please merge this change-set if you think it is ready. I will proceed with 5.4a1 later today. |
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.
Add experimental
RouteSegmentedConnPool(OFFLOCK): lock-free, route-segmented, disposal off the hot path; semantics remain compatible with STRICT/LAX.