From: Luca Boccassi <bluca@debian.org>
To: "announce@dpdk.org" <announce@dpdk.org>
Subject: [dpdk-announce] DPDK 16.11.11 released
Date: Fri, 15 Nov 2019 14:06:15 +0000 [thread overview]
Message-ID: <45204014565f946520a8ac2d774050e839e60193.camel@debian.org> (raw)
Hi all,
Here is a new stable release:
https://fast.dpdk.org/rel/dpdk-16.11.11.tar.xz
The git tree is at:
https://dpdk.org/browse/dpdk-stable/?h=16.11
This release fixes an errata in the previous 16.11.10 release that
caused a regression with vhost.
The fix was tested by Intel via the virtio/vhost regression tests:
http://doc.dpdk.org/dts/test_plans/virtio_pvp_regression_test_plan.html
http://doc.dpdk.org/dts/test_plans/vhost_dequeue_zero_copy_test_plan.html
http://doc.dpdk.org/dts/test_plans/vm2vm_virtio_pmd_test_plan.html
Luca Boccassi
---
doc/guides/rel_notes/release_16_11.rst | 22 +++++++++++++++++++
---
lib/librte_eal/common/include/rte_version.h | 2 +-
lib/librte_vhost/vhost_user.c | 13 ++++++++++---
pkg/dpdk.spec | 2 +-
4 files changed, 31 insertions(+), 8 deletions(-)
Luca Boccassi (1):
version: 16.11.11
Zhike Wang (1):
vhost: fix vring requests validation broken if no FD
--
Kind regards,
Luca Boccassi
reply other threads:[~2019-11-15 14:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45204014565f946520a8ac2d774050e839e60193.camel@debian.org \
--to=bluca@debian.org \
--cc=announce@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).