Ubuntu
dpdk package

Upgrade to DPDK 17.05 in Artful

Bug #1691661 reported by Christian Ehrhardt 
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
dpdk (Ubuntu)
Fix Released
High
Christian Ehrhardt 
openvswitch (Ubuntu)
Won't Fix
High
Christian Ehrhardt 

Bug Description

Upgrading to DPDK 17.05 would be a good match for the release timing of artful.
This should allow us to shove in the first stable release 17.05.1 around September for extra stability.

We are working on DPDK 17.05 in general at the deb_dpdk project and things seem to work, but being a rather complex lib this has more implications like at the moment Openvswitch even on 2.7 not working with it.

So evaluate and work on that.

Christian Ehrhardt  (paelzer)
Changed in dpdk (Ubuntu):
status: New → Triaged
importance: Undecided → High
assignee: nobody → ChristianEhrhardt (paelzer)
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Extra task for the Openvswitch work that seems to not like the new includes.

Changed in openvswitch (Ubuntu):
status: New → Confirmed
importance: Undecided → High
assignee: nobody → ChristianEhrhardt (paelzer)
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

OVS need to adapt to new DPDK in general for ABI and header changes as outlined in:

http://dpdk.org/doc/guides/rel_notes/release_17_05.html#api-changes
http://dpdk.org/doc/guides/rel_notes/release_17_05.html#abi-changes

I need to check if that code is already in OVS later and can be backported, otherwise we might be blocked here for now and only continue to update DPDK itself with the open task to close the full transition once we think we can.

Changed in openvswitch (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Well it seems I was a bit overeager to target 17.05 as we eventually have to follow the use-case which is mostly openvswitch for now.

But while exploitation was rather fast in the past given that OVS dropped the experimental state from DPDK support this got more official now.

So in [1] one can see that OVS 2.7 only plans to support DPDK 16.11.
We should not derive too much from that as history told us that causes too much errors.

That means:
- deb_dpdk project will continue to work on DPDK 17.05 into Debian experimental (out of experimental after unfrozen)
- For Artful which is bound to OVS 2.7 we will re-align DPDK and focus on the next LTS release which is 16.11.2
- The enablement we planned can be done there, some arm backports needed but ok since they are upstream.

[1]: http://docs.openvswitch.org/en/latest/faq/releases/

Changed in openvswitch (Ubuntu):
status: Triaged → Won't Fix
Changed in dpdk (Ubuntu):
status: Triaged → Won't Fix
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package dpdk - 17.05.1-2

---------------
dpdk (17.05.1-2) experimental; urgency=medium

  * Install headers with arch-specific content in /usr/include/<multiarch>/dpdk
    to make libdpdk-dev multiarch-compliant.
    To ensure backward compatibility in x86_64, which is what most of the
    consumers use, symlink x86_64 headers in /usr/include/dpdk.
    pkg-config returns the arch-specific headers first so that other
    architectures are still compatible.
    Also create a full copy of the headers in the dpdk-dev SDK package, as it
    does not support multiple levels of headers.

 -- Luca Boccassi <email address hidden> Wed, 09 Aug 2017 13:02:28 +0100

Changed in dpdk (Ubuntu):
status: Won't Fix → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.