@@ -60,15 +60,23 @@ Test commands used for running stress-ng and cyclictest together
60
60
61
61
The latencies observed with this DK are summarized below:
62
62
63
+ .. note ::
64
+
65
+ A known issue in this SDK release is affecting this benchmark.
66
+ Applying `this patch `_ on Yocto's meta-ti layer will restore the
67
+ context switch latencies to the values you see below.
68
+
63
69
.. csv-table ::
64
70
:header: "Latencies","CPU 0","CPU 1"
65
71
66
72
"Minimum (usec)","6","6"
67
- "Average (usec)","8 ","8 "
68
- "Maximum (usec)","77","105 "
73
+ "Average (usec)","10 ","9 "
74
+ "Maximum (usec)","77","52 "
69
75
70
76
.. image :: img/rt-cpu-method-all-latency-histogram.png
71
77
78
+ .. _this patch : https://lists.yoctoproject.org/g/meta-ti/message/19089
79
+
72
80
|
73
81
74
82
LMBench
@@ -791,8 +799,8 @@ RP Message Inter-Processor Communication (IPC) Latency
791
799
RP Message latency Performance
792
800
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
793
801
794
- RP Message latency is the delay measured from sending a round trip echo message from
795
- a Linux application to a remote processor and back. The following measurements use
802
+ RP Message latency is the delay measured from sending a round trip echo message from
803
+ a Linux application to a remote processor and back. The following measurements use
796
804
a RP message length of 1 byte and 490 bytes for comparison.
797
805
798
806
The Linux user space application `rpmsg_char_benchmark <https://git.ti.com/cgit/rpmsg/ti-rpmsg-char/ >`__ captures these latency values.
0 commit comments