Seems like a welcome, logical, incremental step towards using DPDK binary packaging.
Would it make sense to always first try to pull and install the binary package from the nexus server.
Only building locally when either the download fails or when forced to do so. Then for those people who are developing using a stable release, they save the unnecessary time of building DPDK? Ray K On 10/01/2017 00:04, Damjan Marion (damarion) wrote:
Currently we are maintaining own set of DPDK patches and building DPDK from source, this is something which will unlikely change short term. Still it is quite time consuming and annoying that we are re-building dpdk over-and-over without real need to do so. I just submitted RFC patch to gerrit[1] which changes this a bit and would like to hear feedback from other people. Changes are: - dpdk is not built anymore during the vpp build process, installed dpdk libs/headers are used instead - I added packaging for dpdk header/libs which generates .deb files. It works in the following way: $ make -C dpdk install-deb Creates and installs (dpkg -i): $ ls dpdk/*.deb dpdk/vpp-dpdk-dbg_16.11-vpp1_amd64.deb dpdk/vpp-dpdk-dev_16.11-vpp1_amd64.deb - this installation process can be part of bootstrap, or people can fetch those debs from nexus server - When we add new patch we simply bump PKG_PREFIX inside dpdk/Makefile to be “vpp2” instead of “vpp1” and so on. Immediately after that (during the next build) people should be warned that they have outdated dpdk package installed. Something like: $ make -C dpdk check-deb make: Entering directory '/home/damarion/src/vpp/dpdk' ========================================================== Outdated DPDK package detected: Installed: vpp-dpdk-dev 16.11-vpp0 Current: vpp-dpdk-dev 16.11-vpp1 Please upgrade by invoking 'make -C dpdk install-deb' ========================================================== - We should support option for people to use instead official DPDK packages, but they should be warned that they might not get optimal performance in all cases. - All written above should also apply for RPMs [1] https://gerrit.fd.io/r/#/c/4613 Thanks, Damjan _______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
