Menu ▾ ▴

#253 UDP empty report triggering packet accounting

1.0
pending
Robert McMahon
None
2023-04-14
2023-04-14
Robert McMahon
No

We found another interesting case that might be another interval corner case. One of the test cases intermittently gets low throughput (assumed driver issue, not iperf!). But the out-of-order and latency look weird.

Always exactly 1 datagram out of order per interval.

Min and Mean latency are very good, but max is always just slightly more than 1 second (which is also the interval).

It’s hard to imagine a genuine traffic pattern with these properties. 

01:31:30.002  LOG   mc33sm701r3 [1] [ ID] Interval        Transfer     Bandwidth      Write/Err  PPS
01:31:30.002  LOG   mc33sm701r3 [1] [  1] 0.00-2.00 sec  21.6 MBytes  90.7 Mbits/sec  15425/0    14666 pps
01:31:32.033  LOG   mc33sm701r2 [1] [  1] 2.00-4.00 sec  8722980 Bytes  34891920 bits/sec   0.000 ms 0/5934 (0%) 3.786/0.639/1015.918/22.747 ms 1945 pps 1152
01:31:32.033  LOG   mc33sm701r2 [1] [  1] 2.00-4.00 sec  1 datagrams received out-of-order
01:31:32.037  LOG   mc33sm701r2 [0] [  1] 2.00-4.00 sec  8032080 Bytes  32128320 bits/sec   0.004 ms 0/5464 (0%) 3.450/0.610/1016.614/23.720 ms 1791 pps 1164
01:31:32.037  LOG   mc33sm701r2 [0] [  1] 2.00-4.00 sec  1 datagrams received out-of-order
01:31:32.049  LOG   mc33sm701r3 [1] [  1] 2.00-4.00 sec  8.32 MBytes  34.9 Mbits/sec  5934/0     2897 pps
01:31:32.052  LOG   mc33sm701r3 [0] [  1] 2.00-4.00 sec  7.66 MBytes  32.1 Mbits/sec  5464/0     2667 pps
01:31:34.078  LOG   mc33sm701r2 [1] [  1] 4.00-6.00 sec  8255520 Bytes  33022080 bits/sec   0.001 ms 0/5616 (0%) 4.094/0.726/1016.168/23.392 ms 1842 pps 1008
01:31:34.078  LOG   mc33sm701r2 [1] [  1] 4.00-6.00 sec  1 datagrams received out-of-order
01:31:34.083  LOG   mc33sm701r2 [0] [  1] 4.00-6.00 sec  8320200 Bytes  33280800 bits/sec   0.001 ms 0/5660 (0%) 3.837/0.675/1016.391/23.308 ms 1856 pps 1084
01:31:34.083  LOG   mc33sm701r2 [0] [  1] 4.00-6.00 sec  1 datagrams received out-of-order

Discussion

  • Robert McMahon

    Robert McMahon - 2023-04-14

    An empty report shouldn't trigger packet accounting. Fix is here

     

    Last edit: Robert McMahon 2023-04-14

  • Robert McMahon

    Robert McMahon - 2023-04-14
    • status: accepted --> pending
     

  • Robert McMahon

    Robert McMahon - 2023-04-14
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -1,4 +1,3 @@
-~~~
 We found another interesting case that might be another interval corner case.  One of Jessica’s test cases intermittently gets low throughput (assumed driver issue, not iperf!).  But the out-of-order and latency look weird.


@@ -6,9 +5,9 @@

 Min and Mean latency are very good, but max is always just slightly more than 1 second (which is also the interval).

+It’s hard to imagine a genuine traffic pattern with these properties. 

-It’s hard to imagine a genuine traffic pattern with these properties. 

- 
+~~~
 01:31:30.002  LOG   mc33sm701r3 [1] [ ID] Interval        Transfer     Bandwidth      Write/Err  PPS
 01:31:30.002  LOG   mc33sm701r3 [1] [  1] 0.00-2.00 sec  21.6 MBytes  90.7 Mbits/sec  15425/0    14666 pps
 01:31:32.033  LOG   mc33sm701r2 [1] [  1] 2.00-4.00 sec  8722980 Bytes  34891920 bits/sec   0.000 ms 0/5934 (0%) 3.786/0.639/1015.918/22.747 ms 1945 pps 1152
     

  • Robert McMahon

    Robert McMahon - 2023-04-14
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -1,5 +1,4 @@
-We found another interesting case that might be another interval corner case.  One of Jessica’s test cases intermittently gets low throughput (assumed driver issue, not iperf!).  But the out-of-order and latency look weird.
-
+We found another interesting case that might be another interval corner case.  One of the test cases intermittently gets low throughput (assumed driver issue, not iperf!).  But the out-of-order and latency look weird.

 Always exactly 1 datagram out of order per interval.
     

Log in to post a comment.

auth0 logo