Subject: [vpp-dev] dpdk drivers
Hi all
I have changed something in the function "eth_em_xmit_pkts", which belong to
e1000 driver.
But I found out that my change does not work. Its object file is
"librte_pmd_e1000.a", but I do not know how it connected to vpp.
What can I do
Hi all
I have changed something in the function "eth_em_xmit_pkts", which belong to
e1000 driver.
But I found out that my change does not work. Its object file is
"librte_pmd_e1000.a", but I do not know how it connected to vpp.
What can I do to make this change effective.
Regards,
Xlangyun
-
Maybe you need to do some visual inspection during the build to check that
what you think is being built is indeed being built and linked. Possibly
you might
[V=1] make build-release > build.log 2>&1
and look in build.log.
Also manually examine timestamps on relevant files along with that. Until
Hi,
I changed DPDK_BUILD_DIR?= $(CURDIR)/dpdk-17.02 and the file
"rte_eth_bond_pmd.c" under this folder.
I also changed dpdk Makefile like this:
$(B)/.extract.ok: $(B)/.download.ok
#@echo --- extracting $(DPDK_TARBALL) ---
#@tar --directory $(B) --extract --file $(CURDIR
Unless you set the DPDK_DOWNLOAD_DIR environment variable, VPP will keep using
the source downloaded in its default location.
Within the vpp repository, at the top-level directory you find a dpdk folder;
try to look at the Makefile in there to understand the logic. Bottom-line: you
need to specify
Hi all,
I'v changed a dpdk driver file which is rte_eth_bond_pmd.c,
Then I would like to compile dpdk to become effiective.
I start vpp with gdb, and use gdb cmd "list slave_configure", there is no
change, I hope to hearing from you.
Here are my operations.
DPDK compile:
export RTE_SDK="/home
