ZeroTier on multiple threads #2233
Closed
Conversation
This file contains 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
only need network and member IDs
Intention was to have (x >= 0 && x <= 8) but rules[rn].v.qosBucket is unsigned (thus always >= 0)
Fix test that was always true
Temporal integration with hosted controllers
remove some debug logging
Update SECURITY.md
On macOS, dump gives this output: % sudo zerotier-cli dump Writing dump to: /Users/brenton/Desktop//zerotier_dump.txt No reason for extra '/' in path
check hooks are enabled before firing
|
Closing due to incorrect base branch. Will re-open a new PR |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
ZeroTier on multiple threads
This alpha-quality patch enables concurrent processing of packets in the RX and TX directions and appears to improve performance significantly in many situations (but also make some worse). It automatically scales thread count according to
std::thread::hardware_concurrency()and can optionally be overridden at start time by setting theZT_PACKET_PROCESSING_CONCURRENCYenvironment variable. You can enable CPU pinning at start time viaZT_CPU_PINNING=1.This has only been tested on Linux and FreeBSD and is not fully implemented in macOS so don't even try.
Example usage (
ZT_PACKET_PROCESSING_CONCURRENCYis entirely optional since it'll automatically use all cores):To force ZeroTier onto one thread: