the diff between mTCP DPDK and upstream DPDK about mtcp HOT 6 CLOSED

it looks like the mTCP github repo contained DPDK build directory and binaries, it make it a little bit difficult to track the mTCP DPDK changes and upstream DPDK

from mtcp.

Sorry Vincent, you were almost there with the patch. You just need to add one more line in mk/rte.cpuflags.mk file (at the end of file):

$(shell echo ${MACHINE_CFLAGS} > ${RTE_SDK}/${RTE_TARGET}/include/cflags.txt)

Recompile dpdk-2.2 toolkit and that should do it.

from mtcp.

Thanks Asim, that solves the problem

from mtcp.

Hi Vincent, I left some comments regarding your pull requests. Did you find time to look at them?

from mtcp.

I ran into this problem today when I was trying to build mTCP with Mellanox DPDK. I solved the problem myself before seeing this thread. Could you please update the documentation to make this problem clear? Basically, people need to copy mtcp/dpdk-X.X/mk/rte.app.mk and mtcp/dpdk-X.X/mk/rte.cpuflags.mk into their dpdk/mk/ directory.

from mtcp.

Hi yilongli,

Sorry to be responding to you this late. This issue is briefly mentioned in the README file. We normally advise the mTCP users to use our version of dpdk because we have patched igb_uio kernel module driver (for Intel-based Ethernet adapters). Since you are using Mellanox cards, you can use any version of dpdk in practice. I will mention about the changes made in rte.app.mk and rte_cpuflags.mk files in the README as well. Thanks!

from mtcp.