From: Thomas Monjalon <thomas@monjalon.net>
To: announce@dpdk.org
Subject: [dpdk-announce] release candidate 17.11-rc1
Date: Sat, 14 Oct 2017 03:01:28 +0200 [thread overview]
Message-ID: <7450449.zjFS65qiAL@xps> (raw)
A new DPDK release candidate is ready for testing:
http://dpdk.org/browse/dpdk/tag/?id=v17.11-rc1
There are 893 patches in this first drop. It is a new record!
It required a lot of work from all the contributors
and especially from Ferruh, thanks :)
The planned release date for 17.11 is in three weeks.
It is time for testing and bug fixing.
It is not expected to integrate a lot more new features at this stage.
However these ones may be part of RC2:
- IOVA scheme wording
- PCI and VDEV move to drivers/bus/
- IPsec offloading with rte_security
- QoS features from dpdk-next-tm
- pipeline improvements
- removals planned in deprecation notices
The release notes are mostly updated:
http://dpdk.org/doc/guides/rel_notes/release_17_11.html
Some highlights:
- ethdev port id increased to 16 bits
- ethdev Rx/Tx offload API reworked
- Marvell Armada drivers
- NXP DPAA1 drivers
- Cavium OcteonTX drivers
- Netronome PF driver
- Mellanox drivers reworked for upstream ibverbs support
- SoftNIC driver for traffic management software fallback
- vhost IOMMU
- GSO library
- Membership library
- Power management updated
- Xen dom0 removed
There are a lot of changes to be tested.
Please pay attention especially to igb_uio with different combinations
of PF or VF drivers.
When finding a new bug, please report it on bugzilla:
http://dpdk.org/tracker/
Thank you everyone
reply other threads:[~2017-10-14 1:01 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=7450449.zjFS65qiAL@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.