-
Notifications
You must be signed in to change notification settings - Fork 165
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
refactor(iroh-net): keep DerpMap
fixed
#1329
Conversation
This was not being done anyway
/// None (or zero regions/nodes) means DERP is disabled. | ||
pub(self) derp_map: tokio::sync::RwLock<Option<DerpMap>>, |
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.
🎆
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.
Looks good. Less locks is more better.
But why exactly don't we need set_derp_map anymore?
it came from the original tailscale design, but we don't actually use it, other than on startup |
Looks like some initial setup pieces are not quite working yet with this change.. |
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.
I do think that in the (distant) future we will likely need something that allows us to add new derp regions to very long running nodes without restarting them, this is much simpler and all we need for now!
Description
The
DerpMap
wasn't being changed anyway at runtime, only for initial config.Closes #1182
Change checklist