Kernel network stack bypass #1
Merged
Conversation
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
f8fb544 to
3ea2084
Compare
3ea2084 to
62be3a8
Compare
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.
Tested on June 15. There were 2 kernel modules, one for each of 2 hosts, and it showed a massive improvement in RTT between two QEMU instances connected on the same host through tap interfaces over a bridge. Userspace ping was ~3ms. Kernelspace raw frame "ping" was 800us.
Additional experiments performed with kernel modules registering a handler for the custom protocol. This removes the need for kernel patching, but adds about 30us in this setup. So we use the simple kernel patch.