From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: thomas@monjalon.net
Subject: Re: [dpdk-dev] [dpdk-announce] release candidate 17.11-rc2
Date: Wed, 1 Nov 2017 16:02:39 +0000 [thread overview]
Message-ID: <20171101160239.GA17708@bricha3-MOBL3.ger.corp.intel.com> (raw)
In-Reply-To: <2876801.5lHDf6jNDb@xps>
On Fri, Oct 27, 2017 at 02:26:52AM +0200, Thomas Monjalon wrote:
> A new DPDK release candidate is ready for testing:
> http://dpdk.org/browse/dpdk/tag/?id=v17.11-rc2
>
> What's new in RC2?
> - igb_uio reset fixed
> - EAL PCI moved to driver and lib
> - Rx offload API for traffic metering and policing (rte_mtr)
> - IPsec offload API (rte_security)
> - NXP and Cavium implementations of event/Rx adapter
> - flow classify library
> - pipeline improvements
> - example app for service cores
>
> The release notes have been updated:
> http://dpdk.org/doc/guides/rel_notes/release_17_11.html
>
> We have been very ambitious (maybe too much) in the RC2 expectations.
> As a consequence, two weeks have passed since the RC1.
> In order to save time in the schedule, we should try to close 17.11
> in less than two weeks. I suggest RC3 to be done next week, November 2.
> The next release candidate is expected to include only some
> bug fixes, tooling, packaging or documentation updates.
>
> This version needs to be tested a lot.
> Please pay a special attention to the mbuf VLAN flags
> PKT_RX_VLAN_PKT and PKT_RX_QINQ_PKT which are deprecated
> and renamed with new meanings.
>
> Thank you everyone
> Happy scary Halloween!
FYI: the dpdk-next-build tree has been rebased to include 17.11-rc2.
There is one new commit on that tree to build the pci bus driver, which
was needed by lots of other drivers, and there have been changes made to
a number of other commits so as to keep the history clean and compiling
patch-by-patch on top of the mainline head.
I'm hoping that for 18.02 release this work can be merged into the main
tree as an "experimental" new feature, to help reduce this ongoing
maintenance work of constant rebasing previous patches. Having it
generally available, I also hope would encourage additional
contributions for drivers and platforms not yet supported in the
next-build tree.
Regards,
/Bruce
prev parent reply other threads:[~2017-11-01 16:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-27 0:26 Thomas Monjalon
2017-11-01 16:02 ` Bruce Richardson [this message]
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=20171101160239.GA17708@bricha3-MOBL3.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).