PPing - Add introduction and figure description #33
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
Update README with an introduction motivating why a BPF implementation of pping is useful. Also add a figure description for the design figure. In general, also refer to Kathie's pping as PPing and our BPF pping as ePPing. Signed-off-by: Simon Sundberg <simon.sundberg@kau.se>
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
The added for this commit was essentially used as a basis for the Red-Hat report, and is also similar to the one found in my PPing poster.
It's probably not a great idea to merge this before PR#32 as this was written with the at the time most current version of ePPing in mind. It indirectly refers to support for the ICMP protocol (which is added in PR#32) and the figure description is for the design figure from PR#32. Therefore I will leave this as a draft for now.