From 3c23979e8770e5d5e6dc104d36f20ea5697f3fcc Mon Sep 17 00:00:00 2001 From: Vratko Polak Date: Mon, 3 Feb 2020 18:51:14 +0100 Subject: Report: Edit minor details in methodology docs Change-Id: I9bbb97e635b6ef438dcb8bed3f69617bb98e9779 Signed-off-by: Vratko Polak --- docs/report/introduction/methodology_packet_latency.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'docs/report/introduction/methodology_packet_latency.rst') diff --git a/docs/report/introduction/methodology_packet_latency.rst b/docs/report/introduction/methodology_packet_latency.rst index b8df660539..1f7ad7f633 100644 --- a/docs/report/introduction/methodology_packet_latency.rst +++ b/docs/report/introduction/methodology_packet_latency.rst @@ -1,7 +1,7 @@ Packet Latency -------------- -TRex Traffic Generator (TG) is used for measuring latency across 2-Node +TRex Traffic Generator (TG) is used for measuring latency across 2-Node and 3-Node SUT server topologies. TRex integrates `A High Dynamic Range Histogram (HDRH) `_ code providing per packet latency distribution for latency streams sent in parallel to the main @@ -30,4 +30,4 @@ methodology: setup used. - TG setup introduces an always-on Tx/Rx interface latency of about 2 * 2 usec per direction induced by TRex SW writing and reading packet - timestamps on CPU cores. \ No newline at end of file + timestamps on CPU cores. -- cgit 1.2.3-korg