summaryrefslogtreecommitdiffstats
path: root/VNFs/DPPD-PROX/config/bng-no-cpu-topology-4ports.cfg
diff options
context:
space:
mode:
authorPatrice Buriez <patrice.buriez@intel.com>2018-09-03 18:55:24 +0200
committerPatrice Buriez <patrice.buriez@intel.com>2018-09-04 16:35:33 +0200
commita3a7fbb44e261987e2cd800fb049c20b16381e4d (patch)
treef15f05a8beef85ef142d7980595aa07ec1aaedde /VNFs/DPPD-PROX/config/bng-no-cpu-topology-4ports.cfg
parent4e70037968d120b27b5360107ef3ab2e5a5f57b7 (diff)
Workaround DPDK net/virtio queue setup issue
JIRA: SAMPLEVNF-127 PROX was crashing in the VM with vector mode enabled and multiple OVS queues. This was not really a PROX bug, but a DPDK issue, which has been fixed by DPDK commit https://git.dpdk.org/dpdk/commit/?id=efc83a1e7fc3 This "net/virtio: fix queue setup consistency" is included in DPDK 17.11 and subsequent versions, and has been backported into: - DPDK 16.11.4: https://git.dpdk.org/dpdk-stable/commit/?h=16.11&id=516447a5056c - DPDK 17.08.1: https://git.dpdk.org/dpdk-stable/commit/?h=17.08&id=907fe4fc263e This means the fix is not included into any DPDK 17.02.x used by NSB. Fortunately, a simple workaround consists of calling rte_eth_tx_queue_setup() before rte_eth_rx_queue_setup(). This change implements this simple workaround, in order to make PROX work, even with unfixed DPDK versions. Change-Id: I818e9bb812babe023c6b7225c8b9769a359d9bec Signed-off-by: Patrice Buriez <patrice.buriez@intel.com>
Diffstat (limited to 'VNFs/DPPD-PROX/config/bng-no-cpu-topology-4ports.cfg')
0 files changed, 0 insertions, 0 deletions