gnrc_sixlowpan_iphc: refactor reception for #8511#9484
Merged
cgundogan merged 1 commit intoRIOT-OS:masterfrom Jul 26, 2018
Merged
gnrc_sixlowpan_iphc: refactor reception for #8511#9484cgundogan merged 1 commit intoRIOT-OS:masterfrom
cgundogan merged 1 commit intoRIOT-OS:masterfrom
Conversation
5126267 to
59daa1e
Compare
This was referenced Jul 3, 2018
Member
Author
|
Also ping @A-Paul. I think this could be interesting regarding GHC. |
Member
Author
|
Note to self: adapt for rename solicited in #9483 (comment), when rebasing. |
59daa1e to
2c6b1cf
Compare
Member
Author
|
Rebased to and adapted for current master. |
Member
Author
|
(since both dependencies are merged this PR is not waiting for another PR anymore) |
2c6b1cf to
f6ecdc8
Compare
This refactors reception/decoding part of `gnrc_sixlowpan_iphc` to the more layered approach modeled in RIOT-OS#8511. Since the reception part is already complicated enough I decided to divide send and receive up into separate changes.
f6ecdc8 to
69d9ecc
Compare
Member
Author
|
Rebased again, since the merging of #9485 created a conflict. |
cgundogan
approved these changes
Jul 26, 2018
Member
cgundogan
left a comment
There was a problem hiding this comment.
Code looks fine and verified that frag/iphc is still working. Tested on the testbed w/ and w/o compiling frag/iphc.
miri64
added a commit
to miri64/RIOT
that referenced
this pull request
Oct 23, 2018
Though this change might seem more complicated, it has the benefit, that after RIOT-OS#9484 we don't have to assume that a received packet within IPv6's receive function can be handed to the function pre-parsed, making that function far less complicated (will be provided in a future PR).
miri64
added a commit
to miri64/RIOT
that referenced
this pull request
Oct 23, 2018
Though this change might seem more complicated, it has the benefit, that after RIOT-OS#9484 we don't have to assume that a received packet within IPv6's receive function can be handed to the function pre-parsed, making that function far less complicated (will be provided in a future PR). Also this might give the forwarding via routing header a little performance boost, as we now don't *receive* the packet first only to forward it later-on.
This was referenced Oct 23, 2018
miri64
added a commit
to miri64/RIOT
that referenced
this pull request
Oct 25, 2018
Though this change might seem more complicated, it has the benefit, that after RIOT-OS#9484 we don't have to assume that a received packet within IPv6's receive function can be handed to the function pre-parsed, making that function far less complicated (will be provided in a future PR). Also this might give the forwarding via routing header a little performance boost, as we now don't *receive* the packet first only to forward it later-on.
miri64
added a commit
to miri64/RIOT
that referenced
this pull request
Oct 25, 2018
Though this change might seem more complicated, it has the benefit, that after RIOT-OS#9484 we don't have to assume that a received packet within IPv6's receive function can be handed to the function pre-parsed, making that function far less complicated (will be provided in a future PR). Also this might give the forwarding via routing header a little performance boost, as we now don't *receive* the packet first only to forward it later-on.
miri64
added a commit
to miri64/RIOT
that referenced
this pull request
Nov 17, 2018
Though this change might seem more complicated, it has the benefit, that after RIOT-OS#9484 we don't have to assume that a received packet within IPv6's receive function can be handed to the function pre-parsed, making that function far less complicated (will be provided in a future PR). Also this might give the forwarding via routing header a little performance boost, as we now don't *receive* the packet first only to forward it later-on.
miri64
added a commit
to miri64/RIOT
that referenced
this pull request
Dec 6, 2018
Though this change might seem more complicated, it has the benefit, that after RIOT-OS#9484 we don't have to assume that a received packet within IPv6's receive function can be handed to the function pre-parsed, making that function far less complicated (will be provided in a future PR). Also this might give the forwarding via routing header a little performance boost, as we now don't *receive* the packet first only to forward it later-on.
crest42
pushed a commit
to crest42/RIOT
that referenced
this pull request
Dec 18, 2018
Though this change might seem more complicated, it has the benefit, that after RIOT-OS#9484 we don't have to assume that a received packet within IPv6's receive function can be handed to the function pre-parsed, making that function far less complicated (will be provided in a future PR). Also this might give the forwarding via routing header a little performance boost, as we now don't *receive* the packet first only to forward it later-on.
BytesGalore
pushed a commit
to BytesGalore/RIOT
that referenced
this pull request
Jan 29, 2019
Though this change might seem more complicated, it has the benefit, that after RIOT-OS#9484 we don't have to assume that a received packet within IPv6's receive function can be handed to the function pre-parsed, making that function far less complicated (will be provided in a future PR). Also this might give the forwarding via routing header a little performance boost, as we now don't *receive* the packet first only to forward it later-on.
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
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.
Contribution description
This refactors reception/decoding part of
gnrc_sixlowpan_iphcto the more layered approach modeled in #8511. Since the reception part is already complicated enough I decided to divide send and receive up into separate changes.Testing
To test I used the
ping6andudp {send|server}server commandtests/gnrc_udpwith different packet sizes and ports (including the NHC UDP compressed range 61616-61631), and also with IPHC (de-)activated withifconfig 6 -iphconsamr21-xpro. I also tested several compile configurations with the following patch (and commenting out the correspondingiphc/fraglines):(just resolves the dependency)
Issues/PRs references
Depends on
#9482(merged) and#9483(merged).Adapts IPHC reception for #8511.