task04: add ICMPv6 stress test #90
Conversation
|
|
||
| ### Result | ||
|
|
||
| All nodes are still running, reachable, and the packet buffer is empty 3 seconds |
There was a problem hiding this comment.
3 seconds because that is the time a fragmented datagram might stay in 6LoWPAN's reassembly buffer before completion is given up.
There was a problem hiding this comment.
How do you determine that the packet buffer is empty ? I tried pktbuf and it returns:
> pktbuf
pktbuf
packet buffer: first byte: 0x20001b18, last byte: 0x20003318 (size: 6144)
position of last byte used: 1672
~ unused: 0x20001b18 (next: 0, size: 6144) ~
I guess the unused means it's empty ?
There was a problem hiding this comment.
No, but the size and position of the unused space [edit](and the fact that there is only one)[/edit] gives you a hint that it is empty: It is at the start of the packet buffer (equals first byte:), its size is equal to the size of the packet buffer ((size: 6144) on top, and its next pointer points to NULL. If data would be in the packet buffer you would see several unused spaces with the data as a hex dump in between those spaces. I guess once you saw the filled state you would know what empty is ;-).
There was a problem hiding this comment.
(try pktbuf on the pinged node while it is pinged; you most likely will see what I mean)
This test is aiming to detect regressions to RIOT-OS/RIOT#10672 and RIOT-OS/RIOT#10701.