Extract UDP native endpoint route slots - #1190
Open
Weidong Cui (wdcui) wants to merge 1 commit into
Open
Conversation
Colocate native UDP endpoint readiness, errors, epoll identity, and lifecycle state behind route-aware slots while preserving the existing external-only behavior. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: b5a1a347-37a8-4246-8bbc-306590921475
|
🤖 SemverChecks 🤖 No breaking API changes detected Note: this does not mean API is unchanged, or even that there are no breaking changes; simply, none of the detections triggered. |
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.
This PR extracts the Linux broker's native UDP endpoint lifecycle behind route-aware slots while preserving the existing external-only behavior. Each endpoint now owns its route and slot identity, descriptor, epoll token and generation, readiness latches, write-blocked state, and sequenced native error state; staging, replacement, retirement, rearming, send, receive, and status handling all use that shared endpoint model. Connected sockets retain only their selected route, unconnected sends keep the existing lazy endpoint reuse and source-port preservation, stale events cannot affect replacement endpoints, and staging failures roll back endpoint and token state. Only the external route is instantiated, so this adds no gateway, policy, configuration, CLI, or observable routing behavior while preparing the lifecycle seam needed by the follow-up gateway-routing PR.