Anuket Project

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Next »


Introduction:

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

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


Testbed:

 Intel POD12 

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




CPU Topology on DUT

Scenarios

Summary of Scenarios:

Scenario

Possible Core-allocations:

Assumptions: Numa-0 (0-15) Numa-1 (16-31)

eth0, eth1 (numa-0) eth2, eth3 (numa-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


TGEN: /etc/trex_ens.yaml

H/W TGEN

S/W TGEN


2

vSwitch: 2

PMDs: 4, 5, 6, 7

(0xF0)

VNF: 22, 23

DUT: eno5, eno6

TGEN: 5, 6

DUT: eno3, eno4

TGEN: ens801f0, ens801f1

TGEN: /etc/trex_ens.yaml

H/W TGEN

S/W TGEN


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, 7

DUT: 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. Try different forwarding VNF
  3. Different Virtual Switch (VPP)
  4. RxQ Affinity.


Notes on Documentation

  1. must view log files, qemu threads need to match the intended scenario for VM -
  2. Christian created qemu command (and documentation) - check this for VM mapping
  3. SR: CT's command is only the host
  4. qemu command line -smp 2 should do this - simulates two Numa Nodes  - need to see how the VM see it's architecture: numactl -h
  • No labels