[tun] implement basic multiqueue tun interface #46
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.
Still need to implement all the available offloading features, we're probably leaving quite a bit of performance on the table. If we are careful we might be able to crack an aggregate of around 20gbit/s but each flow will individually limited to ~2-3gbit/s.
Perf testing of two TUN interfaces on a
c7g.metalec2 box. peaks at around 15gbit/sWe're probably being in part limited by the single queue
connection.Pipe()implementation, notably slower on the graviton than my personal laptop.Also I'd try to avoid
TUNSETSTEERINGEBPF, if we can get the application to use the same sending queue for each flow we don't need to worry too much about steering. Might get a little tricky but doing this in userspace might be doable?