dc7680e859
Integrate accelerated networking support into netvsc PMD. This allows netvsc to manage VF without using failsafe or vdev_netvsc. For the exception vswitch path some tests like transmit get a 22% increase in packets/sec. For the VF path, the code is slightly shorter but has no real change in performance. Pro: * using netvsc is more like other DPDK NIC's * the exception packet uses less CPU * much smaller code size * no locking required on VF transmit/receive path * no legacy Linux network device to get mangled by userspace * much simpler (1K vs 9K) LOC * unified extended statistics Con: * using netvsc has more complex startup model * no bifurcated driver support * no flow support (since host does not have flow API). * no tunnel offload support * no receive interrupt support Signed-off-by: Stephen Hemminger <sthemmin@microsoft.com>
25 lines
640 B
Makefile
25 lines
640 B
Makefile
# SPDX-License-Identifier: BSD-3-Clause
|
|
|
|
include $(RTE_SDK)/mk/rte.vars.mk
|
|
|
|
LIB = librte_pmd_netvsc.a
|
|
|
|
CFLAGS += -O3 $(WERROR_FLAGS)
|
|
CFLAGS += -DALLOW_EXPERIMENTAL_API
|
|
|
|
EXPORT_MAP := rte_pmd_netvsc_version.map
|
|
|
|
LIBABIVER := 1
|
|
|
|
SRCS-$(CONFIG_RTE_LIBRTE_NETVSC_PMD) += hn_ethdev.c
|
|
SRCS-$(CONFIG_RTE_LIBRTE_NETVSC_PMD) += hn_rxtx.c
|
|
SRCS-$(CONFIG_RTE_LIBRTE_NETVSC_PMD) += hn_rndis.c
|
|
SRCS-$(CONFIG_RTE_LIBRTE_NETVSC_PMD) += hn_nvs.c
|
|
SRCS-$(CONFIG_RTE_LIBRTE_NETVSC_PMD) += hn_vf.c
|
|
|
|
LDLIBS += -lrte_eal -lrte_mbuf -lrte_mempool -lrte_ring
|
|
LDLIBS += -lrte_ethdev -lrte_net -lrte_kvargs
|
|
LDLIBS += -lrte_bus_vmbus
|
|
|
|
include $(RTE_SDK)/mk/rte.lib.mk
|