Skip to content
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

listener: enable UdpListenerWorkerRouter to support multiple addresses #21940

Merged
merged 8 commits into from
Jun 30, 2022

Conversation

soulxu
Copy link
Member

@soulxu soulxu commented Jun 29, 2022

Commit Message: listener: enable UdpWorkerRouter to support multiple addresses
Additional Description:
This PR enable the ListenerImpl to create UdpListenerWorkerRouter for each address. And pass the correct UdpListenerWorkerRouter to the ActiveUdpListener.

Risk Level: high
Testing: unittest
Docs Changes: n/a
Release Notes: n/a
Platform Specific Features: n/a
Part of #11184

soulxu added 5 commits June 27, 2022 06:44
Signed-off-by: He Jie Xu <[email protected]>
Signed-off-by: He Jie Xu <[email protected]>
Signed-off-by: He Jie Xu <[email protected]>
Signed-off-by: He Jie Xu <[email protected]>
@soulxu soulxu changed the title listener: enable UdpWorkerRouter to support multiple addresses listener: enable UdpListenerWorkerRouter to support multiple addresses Jun 29, 2022
@soulxu
Copy link
Member Author

soulxu commented Jun 29, 2022

/assign @mattklein123

Signed-off-by: He Jie Xu <[email protected]>
Copy link
Member

@mattklein123 mattklein123 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM with small comment, thank you.

/wait

@@ -494,6 +499,7 @@ class ListenerImpl final : public Network::ListenerConfig,

Quic::QuicStatNames& quic_stat_names_;
MissingListenerConfigStats missing_listener_config_stats_;
uint32_t concurrency_;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: const. As an aside it would be nice to not have to store this in every listener, but there probably isn't a great way to do that without passing through all server options so I guess it's ok.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think I can get that from the server instance directly, let me try, also thanks point this out, it indeed better to not pass through it, and it doesn't feel like something the ListenerImpl need to hold one.

Signed-off-by: He Jie Xu <[email protected]>
Copy link
Member

@mattklein123 mattklein123 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@mattklein123 mattklein123 merged commit 330833e into envoyproxy:main Jun 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants