@@ -58,14 +58,25 @@ Test commands used for running stress-ng and cyclictest together
5858   stress-ng --cpu-method=all -c 4 & 
5959   cyclictest -m -Sp80 -D6h -h400 -i200 -M -q 
6060
61- 
61+ 
62+ default SDK image:
63+ 
64+ .. note ::
65+ 
66+    A known issue in this SDK release is affecting this benchmark.
67+    Using OP-TEE's PRNG drivers rather than the hardware accelerated TRNG
68+    drivers restores the context switch latencies to the values you see
69+    here.
70+ 
71+    More information on switching to the PRNG drivers can be found in the
72+    Foundational Components section, here :ref: `building-optee-with-prng `
6273
6374.. csv-table ::
6475   :header:  "Latencies","CPU 0","CPU 1"
6576
6677   "Minimum (usec)","6","6"
67-    "Average (usec)","8 ","8 "
68-    "Maximum (usec)","77","105 "
78+    "Average (usec)","10 ","9 "
79+    "Maximum (usec)","77","52 "
6980
7081.. image :: img/rt-cpu-method-all-latency-histogram.png 
7182
@@ -791,8 +802,8 @@ RP Message Inter-Processor Communication (IPC) Latency
791802RP Message latency Performance
792803^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
793804
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  
805+ RP Message latency is the delay measured from sending a round trip echo message from
806+ a Linux application to a remote processor and back. The following measurements use
796807a RP message length of 1 byte and 490 bytes for comparison.
797808
798809The Linux user space application `rpmsg_char_benchmark  <https://git.ti.com/cgit/rpmsg/ti-rpmsg-char/ >`__ captures these latency values.
0 commit comments