From 7f666d1ac67abdafd91ae1b3dc31010f6c28c62f Mon Sep 17 00:00:00 2001 From: "Mark D. Gray" Date: Thu, 26 May 2016 14:45:20 +0100 Subject: specs: Add "Testing" section to High Priority Datapath spec Change-Id: I47833cd38592636aa052147e356d1df15a0ba452 Signed-off-by: Mark D. Gray --- specs/High-Priority-Traffic-Path.rst | 66 +++++++++++++++++++++++++++++++++++- 1 file changed, 65 insertions(+), 1 deletion(-) diff --git a/specs/High-Priority-Traffic-Path.rst b/specs/High-Priority-Traffic-Path.rst index 25f6361..6243cbe 100644 --- a/specs/High-Priority-Traffic-Path.rst +++ b/specs/High-Priority-Traffic-Path.rst @@ -151,7 +151,71 @@ TBD Testing ======= -TBD +In order to test how effectively the virtual switch handles high priority traffic +types, the following scheme is suggested.:: + + +---------------------------+ Ingress Traffic Parameters + | | +-------------------------------------------+ + | | + | | Packet Size: The size of the Ethernet frames + | | + | | Tmax: RFC2544 Max. Throughput for traffic of + | PHY0 <-------+ "Packet Size" + | | + | | Total Offered Rate: The offered rate of both + | | traffic classes combined expressed as a % of + | | Tmax + | | + | | Ingress Rates are expressed as a percentage + | | of Total Offered Rate. + | | + | | Class A: + | OVS | Ethernet PCP = 0 (Background) + | (BR0) | Ingress Rate : rate_ingress_a(n) Mfps + | | + | | Class B: + | | Ethernet PCP = 7 (Highest) + | | Ingress Rate : rate_ingress_b(n) Mfps + | | + | | Egress Traffic Measurements + | | +-------------------------------------------+ + | | Class A: + | | Egress Throughput : rate_egress_a(n) Mfps + | | Egress Latency : max_lat_egrees_a(n) ms + | | Egress Jitter : max_jit_egress_a(n) ms + | PHY1 +-------> + | | Class B: + | | Egress Throughput : rate_egress_b(n) Mfps + | | Egress Latency : max_lat_egrees_b(n) ms + +---------------------------+ Egress Jitter : max_jit_egress_b(n) ms + + +Open vSwitch is configured to forward traffic between two ports agnostic to the +traffic type. For example, using the following command: + +ovs-ofctl add-flow br0 in_port=0,actions=output:1 + +The test will be carried out with the functionality to enable high-priority +traffic enabled and disabled in order to guage the change in performance for +both cases. + +Two classes of traffic will be generated by a traffic generator. In the example +above, the classes are differentiated using the Ethernet PCP field. However, +another means for differentiating traffic could be used, depending the +prioritization scheme that is developed. + +Tests should be performed for each combination of: + +* Packet Sizes in (64, 512) +* Total Offered Rate in (80, 120, 150) +* rate_ingress_b(n) / rate_ingress_a(n) in (0.1, 0.2, 0.5) + +For each set, the following metrics should be collected for each traffic +class over a specified time period: + +Egress Throughput (Mfps) +Maximum Egress Latency (ms) +Maximum Egress Jitter (ms) Documentation Impact ==================== -- cgit 1.2.3-korg