Fix conjunction in tcp_output_really_helper, adjust to specification #40
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.
Not sure if this is the right patch, but we (/cc @reynir) spent the day looking at Sequences and Acknowledge numbers to realize that at one point, the unikernel's Sequence was decrementing. The comment above specifies that this should be the case if we receive FIN, which is not our case. I think that, due to the associativity of the
||
and&&
operators, the result of the condition becomes true and µTCP decrements the Sequence when it shouldn't. So we've just added parenthesis (by feelings).With this fix, we can do a test with
iperf3
of our unikernel (which claims a speed of 2Mbytes/s... but that's another problem).