From: Thomas Monjalon <thomas@monjalon.net>
To: announce@dpdk.org
Subject: [dpdk-announce] release candidate 17.11-rc3
Date: Wed, 08 Nov 2017 03:27:15 +0100 [thread overview]
Message-ID: <2026159.XyRgl3NqdL@xps> (raw)
A new DPDK release candidate is ready for testing:
http://dpdk.org/browse/dpdk/tag/?id=v17.11-rc3
What's new in RC3?
- igb_uio reset fixed again
- EAL VDEV moved to bus driver
- EAL, mempool and mbuf adapted to IOVA wording
- rte_memcpy optimization reverted because of bad perf
- vhost IOMMU disabled by default because of old Qemu
- example app and how-to for rte_flow API
The release notes have been updated:
http://dpdk.org/doc/guides/rel_notes/release_17_11.html
It was not a quiet release candidate.
More than a week has passed since the RC2.
We must try to make a RC4 and close the 17.11 release in few days
because of the US summit next week.
The next release candidate is expected to include only some
very important bug fixes or documentation updates.
In order to prepare the next release, the deprecation notices
must be reviewed, and the roadmap topics proposed on the mailing list.
Please test carefully this release candidate.
Thank you everyone
reply other threads:[~2017-11-08 2:27 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=2026159.XyRgl3NqdL@xps \
--to=thomas@monjalon.net \
--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).