> From: lukego at gmail.com [mailto:lukego at gmail.com] On Behalf Of Luke > Gorrie > > > On 16 April 2015 at 12:38, O'Driscoll, Tim <tim.o'driscoll at intel.com> > > wrote: > > Following the launch of DPDK by Intel as an internal development project, > > the launch of dpdk.org by > > 6WIND in 2013, and the first DPDK RPM packages for Fedora in 2014, 6WIND, > > Red Hat and Intel would > > like to prepare for future releases after DPDK 2.0 by starting a discussion > > on its evolution. Anyone > > is welcome to join this initiative. > > Thank you for the open invitation. > > I have a couple of questions about the long term of DPDK: > > 1. How will DPDK manage overlap with other project over time? > > In some ways DPDK is growing more overlap with other projects e.g. > forking/rewriting functionality from > Linux (e.g. ixgbe), FreeBSD (e.g. Broadcom PMD), GLIBC (e.g. memcpy). > > In other ways DPDK is delegating functionality to external systems instead > e.g. the bifurcated driver > (delegate to kernel) and Mellanox PMD (delegate to vendor shared library). > > How is this going to play out over the long term? And is there an existential > risk that it will end up > being easier to port the good bits of DPDK into the kernel than the rest of > the good bits of the kernel > into DPDK?
Good question. I don't have a good answer to this, but it is something we will need to consider. Perhaps others have opinions? > 2. How will DPDK users justify contributing to DPDK upstream? > > Engineers in network equipment vendors want to contribute to open source, but > what is the incentive for > the companies to support this? This would be easy if DPDK were GPL'd (they > are compelled) or if everybody > were dynamically linking with the upstream libdpdk (can't have private > patches). However, in a world where > DPDK is BSD-licensed and statically linked, is it not both cheaper and > competitively advantageous to keep > fixes and optimizations in house? > > Today the community is benefiting immensely from the contributions of > companies like 6WIND and Brocade, > but I wonder if this going to be the exception or the rule. That's another good question. Expanding the community and soliciting more contributions is one of the reasons for initiating this discussion. At first glance, it can seem cheaper and competitively advantageous for people to keep DPDK enhancements/optimisations in house. However, that's not necessarily the case. There is an advantage in upstreaming these changes because firstly others in the community may contribute further enhancements, and also because it makes upgrading to new DPDK versions easier because those enhancements will be a core part of DPDK rather than having to be ported separately to new DPDK versions. > That's all from me. Thanks for listening :-). Thanks for contributing your views.
