> Sounds like you want something like libc, but DPDK is a system like a user > space OS more then it is a collection of functions that are independent > like strlen, strcpy, memcpy, printf or ... Some parts of DPDK are > independent and can be used as you suggest, but the real performance > sections are tied together. > > >> Regards, > >> ++Keith
This is indeed quite a statement. DPDK is not just a bunch of NIC drivers, but "a user space OS" (DPDK 1.0 had a baremetal boot: why did it disappeared?). Why Linux or Windows do not integrate DPDK concepts to catch up performance wise? Is it something so deep like the "Big Kernel Lock" that took so many years to get rid of? My assumption is that all current kernels have been built with one implicit hypothesis: the memory is much faster than cpu. This is the opposite today. DPDK internal structure has been adapted to the new paradigm where the TLBs, the memory bandwidth are the scarce resources to manage. So I guess Linux and Windows will not be able to integrate DPDK concepts for performance anytime soon, if ever... Reading the list carefully, I expect disk block PMDs (and block framework?) to come next. Beyond DPDK 2.0: is it time to accept the fact that DPDK community is actually paving the way to the next generation lightweight, high performance, para-virtualized OS? Is it a DPDK task? Another project ? Should we rename DPDK to PVDK? - HK
