** Description changed: *** Still processing FFE and filling in the template *** [Availability] The source code is available from: git://dpdk.org/dpdk General information: http://dpdk.org The package is already part of universe and builds for the target architecture https://launchpad.net/ubuntu/+source/dpdk/2.0.0-0ubuntu1 + [Rationale] The DPDK library will be a build dependency for openvswitch package (extra variant using DPDK instead of kernel network stack). So it will be useful for a large part of our user base around OpenStack. Potentially there will be more projects doing the same, so this should be part of the endorsed set of packages. + [Security] As of today there are no known CVEs nor any advisories on Secunia. There is only one /sbin executable in the form of /sbin/dpdk_nic_bind to get a hold on the network devices. There is one service that gets started in the form of /etc/init.d/dpdk which eventually comes down to "/lib/dpdk/dpdk-init --start" It does not have privileged privileged ports (ports < 1024) bound. [Quality assurance] - While configuration is quite complex, since the dpdk package itself is only a library it does not require *user* configuration. That is a job of the consumers of the library e.g. openvswitch-openstack-dpgk. + While configuration is quite complex, since the dpdk package itself is only a library it does not require *user* configuration. That is a job of the consumers of the library e.g. openvswitch-switch-dpdk. There are no long-term outstanding bugs which affect the usability of the program to a major degree. Upstream is very active and supports and cares for the package. There is no Debian package to consider and the Ubuntu bug tracking system currently only hold this MIR request as an open bug. https://bugs.launchpad.net/ubuntu/+source/dpdk The package in the meantime supports various network cards and even virtio-net so not only exotic hardware that we cannot support. - The package ships a test suite http://dpdk.org/doc/dts/gsg/config.html but it is extremely complex and therefore does not qualify for a build level verification. Still it could and should one day become part of manual QA on that package. - There is a quick test which requires network, but not really network access (to the outside) that might be possible to implement as a Dep8 test for build time http://dpdk.org/doc/quick-start + The package ships a test suite http://dpdk.org/doc/dts/gsg/config.html + but it is extremely complex and therefore does not qualify for a build + level verification. Still it could and should one day become part of + manual QA on that package. - TODO - clarify with Stefan: the package should either provide a - debian/README.source file or a debian/watch file (with comments only) - providing clear instructions on how to generate the source tar file. + There is a quick test which requires network, but not really network + access (to the outside) that might be possible to implement as a Dep8 + test for build time http://dpdk.org/doc/quick-start + + Due to the nature of this "only" being a library real tests should and + to some extend can only be handled in the consuming packages like + openvswitch-switch-dpdk + + There is no debian/README.source file or a debian/watch file providing + clear instructions on how to generate the source tar file, but Stefan is + working on that (Target End of November) + [UI Standards] - This does not apply to a library, so we should be fine on this part. + Does not apply to a library + [Dependencies] texlive-fonts-extra is in universe - we are currently working on removing that dependency (Plan end of November) + [Standards compliance] As of today the upstream version has some conflicts regarding the FHS compliance related to the positioning and versioning of headers and libraries. - We won't be able to change that without a tremendous unmaintainable ubuntu delta to upstream. - This was discussed and upstream DPDK is willing to accept patches to fix that. But due to the roadmap it won't be possible to get that soon enough for the initial release of xenial - but at least it is being worked on and will one day comply. - TODO - check FSH in detail - TODO - check Debian policy + + This was discussed and upstream DPDK is willing to accept patches to fix + that. But due to the roadmap it won't be possible to get that soon + enough for the initial release of this packet in main with xenial - but + at least it is being worked on and will one day comply without so much + Ubuntu delta. + + The current packaging tries to minimize this as much as possible: + - libdpdk - only the lib in standard path /lib + - the lib there is kind of the lowest denominator, only requires sse3 + - the library tries to detect on load and opimizes as good as possible + - some further optimizations need upstream changes to enhance detection + (gnu ifunc?) + - libdpdk-dev - provides the header in standard pfad - /usr/include/dpdk + - dpdk-dev - represents the way upstream handles it but with all content + - below /usr/share/dpdk. Links back to the other two packages to avoid + redundancy + + What is missing is proper so library versions, but we can't define those + without upstream. + + FYI - In Kernel we already have drivers for virtual function I/O and pci + based cards. So there is no need to per device libraries as it was in + the beginning. + + There is no major violation of the Debian policy and not a lot of + conflict since there is no Debian package as of today. + [Maintenance] - TODO - clarify with Stefan + The Server Team will be responsible. + + [Background information] - Of the produced binary packages only libdpdk0 and libdpdk-dev would be required to be in main. The texlive-fonts-extra build dependency only is required to process the dpkd-doc binary(-indep) package. + General purpose of the package is a performance improvement on handling network packets in userspace. - Can we only put the source and both library package into main and by - that avoid the dependency issue? + Of the produced binary packages only libdpdk0 and libdpdk-dev would be + required to be in main. The texlive-fonts-extra build dependency only is + required to process the dpkd-doc binary(-indep) package - but we work on + removing it the dependency anyway.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1492186 Title: [MIR] dpdk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1492186/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
