diff options
| author |   Christian Trautman <ctrautma@redhat.com> | 2016-07-22 15:54:18 -0400 |
|---|---|---|
| committer |   Maryam Tahhan <maryam.tahhan@intel.com> | 2016-08-24 08:43:16 +0000 |
| commit | 0fb65d2afadad1f092788f5a4f251b09851b3ae7 (patch) | |
| tree | 33a8fa5f6dd575d30bc748deb137433a53031218 /conf/04_vnf.conf | |
| parent | bd8712a917d9a0c7272506fd85816f857c32529e (diff) | |
Vanilla_Multi_Queue: Add vanilla ovs multi-queue functionality
Adds multi-queue for vanilla OVS using virtio-net.
TunTap ports will use multi_queue parameter when ports are
created/deleted if guest nic queues are enabled and
vswitch is ovs vanilla. Virtio net will now add guest nic
queues to qemu command line if appropriate.
Reworked multi-queue documentation to reflect these changes.
Adds vhost net thread affinitization which is recommended
when performing vanilla ovs multi-queue.
Guests will require ethtool if using l2fwd or linux bridge
as the loopback application when vanilla ovs multi-queue
is enabled.
Modified dpdk setting in vswitch conf to be better worded
for separation from vanilla ovs multi-queue.
Updated release and installation doc for new vloop image
that includes required ethtool utility.
JIRA: VSPERF-373
Change-Id: Idb550515190b1a93390308c11f54da368f962512
Signed-off-by: Christian Trautman <ctrautma@redhat.com>
Diffstat (limited to 'conf/04_vnf.conf')
| -rw-r--r-- | conf/04_vnf.conf | 11 |
1 files changed, 10 insertions, 1 deletions
diff --git a/conf/04_vnf.conf b/conf/04_vnf.conf index 8069ef0d..05893fb8 100644 --- a/conf/04_vnf.conf +++ b/conf/04_vnf.conf @@ -119,9 +119,18 @@ GUEST_SMP = ['2', '2', '2', '2', '2', '2'] GUEST_CORE_BINDING = [(6, 7), (9, 10), (11, 12), (13, 14), (15, 16), (17, 18)] # Queues per NIC inside guest for multi-queue configuration, requires switch -# multi-queue to be enabled. Set to 0 for disabled. +# multi-queue to be enabled for dpdk. Set to 0 for disabled. Can be enabled if +# using Vanilla OVS without enabling switch multi-queue. GUEST_NIC_QUEUES = 0 +# Virtio-Net vhost thread CPU mapping. If using vanilla OVS with virtio-net, +# you can affinitize the vhost-net threads by enabling the below setting. There +# is one vhost-net thread per port per queue so one guest with 2 queues will +# have 4 vhost-net threads. If more threads are present than CPUs given, the +# affinitize will overlap CPUs. +VSWITCH_VHOST_NET_AFFINITIZATION = False +VSWITCH_VHOST_CPU_MAP = [4,5,8,11] + GUEST_START_TIMEOUT = 120 GUEST_OVS_DPDK_DIR = '/root/ovs_dpdk' OVS_DPDK_SHARE = '/mnt/ovs_dpdk_share' |