2018-01-23 14:21:16 +00:00
|
|
|
# SPDX-License-Identifier: BSD-3-Clause
|
|
|
|
# Copyright(c) 2010-2016 Intel Corporation
|
2014-05-14 14:58:07 +00:00
|
|
|
|
2016-03-04 18:11:12 +00:00
|
|
|
#include "common_base"
|
|
|
|
|
2014-05-14 14:58:07 +00:00
|
|
|
CONFIG_RTE_EXEC_ENV="linuxapp"
|
|
|
|
CONFIG_RTE_EXEC_ENV_LINUXAPP=y
|
|
|
|
|
2017-06-29 05:59:19 +00:00
|
|
|
CONFIG_RTE_EAL_NUMA_AWARE_HUGEPAGES=y
|
2014-06-13 14:52:40 +00:00
|
|
|
CONFIG_RTE_EAL_IGB_UIO=y
|
2014-06-13 14:52:42 +00:00
|
|
|
CONFIG_RTE_EAL_VFIO=y
|
2015-08-03 16:12:17 +00:00
|
|
|
CONFIG_RTE_KNI_KMOD=y
|
2016-03-04 18:11:12 +00:00
|
|
|
CONFIG_RTE_LIBRTE_KNI=y
|
2017-02-17 13:42:38 +00:00
|
|
|
CONFIG_RTE_LIBRTE_PMD_KNI=y
|
2015-06-29 15:58:53 +00:00
|
|
|
CONFIG_RTE_LIBRTE_VHOST=y
|
2017-06-29 05:59:20 +00:00
|
|
|
CONFIG_RTE_LIBRTE_VHOST_NUMA=y
|
vhost: add driver on top of the library
The patch introduces a new PMD. This PMD is implemented as thin wrapper
of librte_vhost. It means librte_vhost is also needed to compile the PMD.
The vhost messages will be handled only when a port is started. So start
a port first, then invoke QEMU.
The PMD has 2 parameters.
- iface: The parameter is used to specify a path to connect to a
virtio-net device.
- queues: The parameter is used to specify the number of the queues
virtio-net device has.
(Default: 1)
Here is an example.
$ ./testpmd -c f -n 4 --vdev 'eth_vhost0,iface=/tmp/sock0,queues=1' -- -i
To connect above testpmd, here is qemu command example.
$ qemu-system-x86_64 \
<snip>
-chardev socket,id=chr0,path=/tmp/sock0 \
-netdev vhost-user,id=net0,chardev=chr0,vhostforce,queues=1 \
-device virtio-net-pci,netdev=net0,mq=on
Signed-off-by: Tetsuya Mukawa <mukawa@igel.co.jp>
Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
Acked-by: Yuanhan Liu <yuanhan.liu@linux.intel.com>
Acked-by: Rich Lane <rich.lane@bigswitch.com>
Tested-by: Rich Lane <rich.lane@bigswitch.com>
Update for queue state event name:
Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2016-03-21 05:45:08 +00:00
|
|
|
CONFIG_RTE_LIBRTE_PMD_VHOST=y
|
net/ifcvf: add ifcvf vDPA driver
The IFCVF vDPA (vhost data path acceleration) driver provides support for
the Intel FPGA 100G VF (IFCVF). IFCVF's datapath is virtio ring compatible,
it works as a HW vhost backend which can send/receive packets to/from
virtio directly by DMA.
Different VF devices serve different virtio frontends which are in
different VMs, so each VF needs to have its own DMA address translation
service. During the driver probe a new container is created, with this
container vDPA driver can program DMA remapping table with the VM's memory
region information.
Key vDPA driver ops implemented:
- ifcvf_dev_config:
Enable VF data path with virtio information provided by vhost lib,
including IOMMU programming to enable VF DMA to VM's memory, VFIO
interrupt setup to route HW interrupt to virtio driver, create notify
relay thread to translate virtio driver's kick to a MMIO write onto HW,
HW queues configuration.
- ifcvf_dev_close:
Revoke all the setup in ifcvf_dev_config.
Live migration feature is supported by IFCVF and this driver enables
it. For the dirty page logging, VF helps to log for packet buffer write,
driver helps to make the used ring as dirty when device stops.
Because vDPA driver needs to set up MSI-X vector to interrupt the
guest, only vfio-pci is supported currently.
Signed-off-by: Xiao Wang <xiao.w.wang@intel.com>
Signed-off-by: Rosen Xu <rosen.xu@intel.com>
Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
2018-04-17 07:06:23 +00:00
|
|
|
CONFIG_RTE_LIBRTE_IFCVF_VDPA_PMD=y
|
2016-03-04 18:11:12 +00:00
|
|
|
CONFIG_RTE_LIBRTE_PMD_AF_PACKET=y
|
2016-12-12 14:38:38 +00:00
|
|
|
CONFIG_RTE_LIBRTE_PMD_TAP=y
|
2017-03-28 11:53:59 +00:00
|
|
|
CONFIG_RTE_LIBRTE_AVP_PMD=y
|
2018-01-18 13:51:42 +00:00
|
|
|
CONFIG_RTE_LIBRTE_VDEV_NETVSC_PMD=y
|
2017-01-13 11:50:02 +00:00
|
|
|
CONFIG_RTE_LIBRTE_NFP_PMD=y
|
2016-03-04 18:11:12 +00:00
|
|
|
CONFIG_RTE_LIBRTE_POWER=y
|
2016-06-15 09:03:22 +00:00
|
|
|
CONFIG_RTE_VIRTIO_USER=y
|
2018-01-12 18:27:29 +00:00
|
|
|
CONFIG_RTE_PROC_INFO=y
|
2018-03-14 07:56:04 +00:00
|
|
|
|
|
|
|
# NXP DPAA BUS and drivers
|
|
|
|
CONFIG_RTE_LIBRTE_DPAA_BUS=y
|
|
|
|
CONFIG_RTE_LIBRTE_DPAA_MEMPOOL=y
|
|
|
|
CONFIG_RTE_LIBRTE_DPAA_PMD=y
|
|
|
|
CONFIG_RTE_LIBRTE_PMD_DPAA_EVENTDEV=y
|
|
|
|
CONFIG_RTE_LIBRTE_PMD_DPAA_SEC=y
|
|
|
|
|
|
|
|
# NXP FSLMC BUS and DPAA2 drivers
|
|
|
|
CONFIG_RTE_LIBRTE_FSLMC_BUS=y
|
|
|
|
CONFIG_RTE_LIBRTE_DPAA2_MEMPOOL=y
|
|
|
|
CONFIG_RTE_LIBRTE_DPAA2_PMD=y
|
|
|
|
CONFIG_RTE_LIBRTE_PMD_DPAA2_EVENTDEV=y
|
|
|
|
CONFIG_RTE_LIBRTE_PMD_DPAA2_SEC=y
|
2018-05-04 10:11:26 +00:00
|
|
|
CONFIG_RTE_LIBRTE_PMD_DPAA2_CMDIF_RAWDEV=y
|
2018-05-03 16:06:07 +00:00
|
|
|
CONFIG_RTE_LIBRTE_PMD_DPAA2_QDMA_RAWDEV=y
|