Skip to content

gnrc_netif: Introduce GNRC_NETIF_HDR_FLAGS_MORE_DATA#9469

Merged
PeterKietzmann merged 1 commit intoRIOT-OS:masterfrom
jnohlgard:pr/netif-flags-more-data
Aug 13, 2018
Merged

gnrc_netif: Introduce GNRC_NETIF_HDR_FLAGS_MORE_DATA#9469
PeterKietzmann merged 1 commit intoRIOT-OS:masterfrom
jnohlgard:pr/netif-flags-more-data

Conversation

@jnohlgard
Copy link
Copy Markdown
Member

Contribution description

Introduce a flag that can be set in the gnrc_netif_hdr_t::flags, gnrc/netif/hdr.h.
The purpose is to use this flag for communicating between the upper layers when there is a burst of TX traffic expected. The first actual usage will be introduced in separate PRs as a part of 6lo fragmentation to set the IEEE 802.15.4 FCF frame pending bit on all but the last fragment.

Issues/PRs references

@jnohlgard jnohlgard added Type: enhancement The issue suggests enhanceable parts / The PR enhances parts of the codebase / documentation Area: network Area: Networking GNRC CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR labels Jun 30, 2018
@jnohlgard jnohlgard added this to the Release 2018.07 milestone Jun 30, 2018
@jnohlgard jnohlgard requested a review from miri64 June 30, 2018 15:52
Copy link
Copy Markdown
Member

@PeterKietzmann PeterKietzmann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Besides the minor comment I'm fine with introducing this flag

/**
* @brief More data will follow
*
* This flag signals that this packet is part of a burst of packets. The link
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comparing to the other flags above, shouldn't this go under @details?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's redundant, details is implicit when a new paragraph is started after the brief description.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Anyhow, for consistency reasons I would leave it in. Or remove the others, but that shouldn't be part of this PR I guess...

* cycled networks to tell the remote node to keep its radio turned on after
* receiving the first fragment.
*
* @see The corresponding bit in the IEEE 802.15.4 frame control field, @ref IEEE802154_FCF_FRAME_PEND
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please break line before @ref.

@jnohlgard
Copy link
Copy Markdown
Member Author

Addressed comments
ping @miri64 @PeterKietzmann

Copy link
Copy Markdown
Member

@miri64 miri64 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK

@miri64
Copy link
Copy Markdown
Member

miri64 commented Aug 12, 2018

Please squash

@jnohlgard jnohlgard force-pushed the pr/netif-flags-more-data branch from 2cdc476 to 29e4a1b Compare August 13, 2018 07:25
@jnohlgard
Copy link
Copy Markdown
Member Author

squashed

@PeterKietzmann PeterKietzmann merged commit 2bfca66 into RIOT-OS:master Aug 13, 2018
@jnohlgard jnohlgard deleted the pr/netif-flags-more-data branch August 14, 2018 08:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area: network Area: Networking CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR Type: enhancement The issue suggests enhanceable parts / The PR enhances parts of the codebase / documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants