Package "dpdk"
WARNING: the "dpdk" package was deleted from this repository
Name: |
dpdk
|
Description: |
Data Plane Development Kit (runtime)
|
Latest version: |
*DELETED* |
Release: |
xenial (16.04) |
Level: |
proposed |
Repository: |
main |
Homepage: |
http://www.dpdk.org |
Links
Download "dpdk"
Other versions of "dpdk" in Xenial
Packages in group
Deleted packages are displayed in grey.
Changelog
dpdk (2.2.0-0ubuntu8) xenial; urgency=medium
* d/p/ubuntu-backport-[36-37] fix virtio issues (LP: #1570195):
- don't let DPDK initialize virtio devices still in use by the kernel
- this avoids conflicts between kernel and dpdk usage of those devices
- an admin now has to unbind/bind devices as on physical hardware
- this is in the dpdk 16.04 release and delta can then be dropped
- d/dpdk-doc.README.Debian update for changes in virtio-pci handling
- d/dpdk.interfaces update for changes in virtio-pci handling
* d/p/ubuntu-backport-38... fix for memory leak (LP: #1570466):
- call vhost_destroy_device on removing vhost user ports to fix memory leak
- this likely is in the dpdk 16.07 release and delta can then be dropped
* d/p/ubuntu-fix-vhost-user-socket-permission.patch fox (LP: #1546565):
- when vhost_user sockets are created they are owner:group of the process
- the DPDK api to create those has no way to specify owner:group
- to fix that without breaking the API and potential workaround code in
consumers of the library like openvswitch 2.6 for example. This patch
adds an EAL commandline option to specify user:group created vhost_user
sockets should have.
-- Christian Ehrhardt <email address hidden> Mon, 25 Apr 2016 11:42:40 +0200
|
1570195 |
Net tools cause kernel soft lockup after DPDK touched VirtIO-pci devices |
1570466 |
Adding/removing ports leaks memory in dpdk |
1546565 |
Ownership/Permissions of vhost_user sockets for openvswitch-dpdk make them unusable by libvirt/qemu/kvm |
|
dpdk (2.2.0-0ubuntu7) xenial; urgency=medium
* Increase max_map_count after setting huge pages (LP: #1507921):
- The default config of 65530 would cause issues as soon as about 64GB or
more are used as 2M huge pages for dpdk.
- Increase this value to base+2*#hugepages to avoid issues on huge systems.
* d/p/ubuntu-backport-[28-32,34-35] backports for stability (LP: #1568838):
- these will be in the 16.04 dpdk release, delta can then be dropped.
- 5 fixes that do not change api/behaviour but fix serious issues.
- 01 f82f705b lpm: fix allocation of an existing object
- 02 f9bd3342 hash: fix multi-process support
- 03 1aadacb5 hash: fix allocation of an existing object
- 04 5d7bfb73 hash: fix race condition at creation
- 05 fe671356 vfio: fix resource leak
- 06 356445f9 port: fix ring writer buffer overflow
- 07 52f7a5ae port: fix burst size mask type
* d/p/ubuntu-backport-33-vhost-user-add-error-handling-for-fd-1023.patch
- this will likely be in dpdk release 16.07 and delta can then be dropped.
- fixes a crash on using fd's >1023 (LP: #1566874)
* d/p/ubuntu-fix-lpm-use-after-free-and-leak.patch fix lpm_free (LP: #1569375)
- the old patches had an error freeing a pointer which had no meta data
- that lead to a crash on any lpm_free call
- folded into the fix that generally covers the lpm allocation and free
weaknesses already (also there this particular mistake was added)
-- Christian Ehrhardt <email address hidden> Tue, 12 Apr 2016 16:13:47 +0200
|
1507921 |
When hugepages is set vm.max_map_count is not automatically adjusted |
1568838 |
Recommended Backports from DPDK 16.04 for DPDK 2.2 - round 2 |
1566874 |
Adding up to MAX_VHOST vhost_user sockets breaks openvswitch-dpdk |
1569375 |
lpm_autotest crashing with dpdk 2.2 |
|
About
-
Send Feedback to @ubuntu_updates