Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Cross-NUMA tests as part of OPNFV Plugfest (Gambia) - January 2019..............

  1. VSPERF-ScenarioScenarios: P2P and PVP.
  2. Workloads: vSwitchd, PMDs and VNF.
  3. VNF: L2 Forwarding
  4. vswitch: OVS and VPP.

...

Node-4 (DUT), Node-5 (Software Traffic Generators) and Ixia H/W Traffic Generator.


CPU Topology on DUT

P2P Scenarios

Image RemovedImage Added

Summary of PVP Scenarios:

Scenario

Possible Core-allocations:
Assumptions: Numa-0 (0-

15

21) Numa-1 (

16

22-43)

vSwitch Core #: 02

DUT Ports, TGen (Hardware) Ports

1

PMDs: 4, 5 (0x30)

DUT: eno5, eno6

TGEN: 5, 6

2

PMDs: 22, 23 (0xC00000)

DUT: eno5, eno6

TGEN: 5, 6

3

PMDs: 4, 22 (0x400010)

DUT: eno5, eno6

TGEN: 5, 6

4

PMDs: 4, 5 (0x30)

DUT: eno5, ens801f2

TGEN: 5, 7

5

PMDs: 22, 23 (0xC00000)

DUT: eno5, ens801f2

TGEN: 5, 7

6

PMDs: 4, 22 (0x400010)

DUT: eno5, ens801f2

TGEN: 5, 7

7

PMDs: 4, 5 (0x30)

DUT: ens801f2, ens802f3

TGEN: 7, 8

8

PMDs: 22, 23 (0xC00000)

DUT: ens801f2, ens802f3

TGEN: 7, 8

9

PMDs: 4, 22 (0x400010)

DUT: ens801f2, ens802f3

TGEN: 7, 8


PVP Scenarios

Image Added

Summary of PVP Scenarios:


31)

eth0, eth1 (numa-0) eth2, eth3 (numa-1)

TGEN: /etc/trex_ens.yaml

H/W TGEN

S/W TGEN

Scenario

Possible Core-allocations:

Assumptions: Numa-0 (0-21) Numa-1 (22-43)


DUT Ports

TGen Ports

(Hardware)

1

DUT Ports

TGen Ports

(Hardware)

DUT Ports

TGen Ports

(Software)

T-Rex Config File to use:DUT Config File to Use

Comments

1

vSwitch: 2

PMDs: 4, 5, 6, 7

(0xF0)

VNF: 8,9

DUT: eno5, eno6

TGEN: 5, 6

DUT: eno3, eno4

TGEN: ens801f0, ens801f1

H/W TGEN

S/W TGEN

2

vSwitch: 2

PMDs: 4, 5, 6, 7

(0xF0)

VNF: 228, 239

DUT: eno5, eno6

TGEN: 5, 6

DUT: eno3, eno4

TGEN: ens801f0, ens801f1

TGEN: /etc/trex_ens.yaml

2

vSwitch: 2

PMDs: 4, 5, 6, 7

(0xF0)

VNF: 22, 23

DUT: eno5, eno6

TGEN: 5, 6

3

vSwitch: 2

PMDs: 4, 5, 6, 7

(0xF0)

VNF: 8, 22

DUT: eno5, eno6

TGEN: 5, 6

DUT: eno3, eno4

TGEN: ens801f0, ens801f1

TGEN: /etc/trex_ens.yaml

H/W TGEN

S/W TGEN

4

vSwitch: 2

PMDs: 4,5,22,23

(0xC00030)

VNF: 8,9

DUT: eno5, ens801f2

TGEN: 5, 7

DUT: eno3, ens801f0

TGEN: ens801f0, eno3

TGEN: /etc/trex_ens_eno.yaml

H/W TGEN

S/W TGEN

5

vSwitch: 2

PMDs: 4,5, 22, 23

(0xC00030)

VNF: 24, 25

DUT: eno5, ens801f2

TGEN: 5, 7DUT: eno3, ens801f0

TGEN: ens801f0, eno3

TGEN: /etc/trex_ens_eno.yaml

H/W TGEN

S/W TGEN

6

vSwitch: 2

PMDs: 4, 5, 22, 23

(0xC00030)

VNF: 8, 24

DUT: eno5, ens801f2

TGEN: 5, 7

DUT: eno3, ens801f0

TGEN: ens801f0, eno3

TGEN: /etc/trex_ens_eno.yaml

H/W TGEN

S/W TGEN

7

vSwitch: 2

PMDs: 22, 23, 24, 25

(0x3C00000)

VNF: 26, 27

DUT: ens801f2, ens802f3

TGEN: 7, 8

DUT: ens801f0, ens801f1

TGEN: eno3, eno4

TGEN: /etc/trex_eno.yaml

H/W TGEN

S/W TGEN

Similar to 1?

8

vSwitch: 2

PMDs: 22, 23, 24, 24

(0x3C00000)

VNF: 4,5

DUT: ens801f2, ens802f3

TGEN: 7, 8

DUT: ens801f0, ens801f1

TGEN: eno3, eno4

TGEN: /etc/trex_eno.yaml

H/W TGEN

S/W TGEN

Similar to 2?

9

vSwitch: 2

PMDs: 22, 23, 24, 25

(0x3C00000)

VNFs: 4,26

DUT: ens801f2, ens802f3

TGEN: 7, 8

DUT: ens801f0, ens801f1

TGEN: eno3, eno4

TGEN: /etc/trex_eno.yaml

H/W TGEN

S/W TGEN

Similar to 3?


Possible Variations

  1. Increase the Number of CPUs to 4 for the VNF.
  2. Phy2phy case (no VNF).
  3. Try different forwarding VNF
  4. Different Virtual Switch (VPP)
  5. RxQ Affinity.

...