gnrc_sixlowpan_frag: Initial import of a fragment size hint feature#11061
Merged
cgundogan merged 1 commit intoRIOT-OS:masterfrom May 28, 2019
Merged
gnrc_sixlowpan_frag: Initial import of a fragment size hint feature#11061cgundogan merged 1 commit intoRIOT-OS:masterfrom
cgundogan merged 1 commit intoRIOT-OS:masterfrom
Conversation
Member
Author
|
#11068 is too experimental so it doesn't make any sense to try to get this into the release => post-poned. |
f7f6808 to
42903e5
Compare
Member
Author
|
Rebased however to resolve conflict with current master |
42903e5 to
8dd85ce
Compare
Member
Author
|
Rebased to current master and dependencies |
Member
Author
|
Rebased to current master and dependencies. |
8dd85ce to
26af0ea
Compare
Member
Author
|
Rebased to current master. |
cgundogan
reviewed
May 28, 2019
Member
Author
|
Reworded the unclear lines. |
098f847 to
5486814
Compare
Member
Author
|
Sorry, accidentally pushed an old version -.- |
Member
Author
|
(it is fixed now) |
cgundogan
reviewed
May 28, 2019
| * payload datagram */ | ||
| #ifdef MODULE_GNRC_SIXLOWPAN_FRAG_HINT | ||
| /** | ||
| * @brief Hint for the size (smaller than link-layer PDU) of for the next |
cgundogan
approved these changes
May 28, 2019
Member
cgundogan
left a comment
There was a problem hiding this comment.
Code looks okay and compiles without errors using the new pseudomodule. ACK.
This allows for sending of fragments smaller than the restrictions set by the link-layer PDU. E.g. to put some slack for IPHC into the first fragment (see https://tools.ietf.org/html/draft-ietf-6lo-fragment-recovery-02#section-4.1).
b6bf984 to
2534cfb
Compare
cgundogan
approved these changes
May 28, 2019
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 allows for sending of fragments smaller than the restrictions set by the link-layer PDU. E.g. to put some slack for IPHC into the first fragment (see https://tools.ietf.org/html/draft-ietf-6lo-fragment-recovery-02#section-4.1).
Testing procedure
Currently there is no test for this (I will provide a test application for my minimal fragment forwarding implementation that also tests this feature), so just compiling
gnrc_networkingwith thegnrc_sixlowpan_frag_hintpseudo-module for a 6Lo-capable board (e.g.samr21-xpro) should suffice (this will not be done by the CI!).Issues/PRs references
Depends on #11021 (mainly because there is a lot of conflict between those two, but functionally it is independent from that PR).