From: Andy Green <andy@warmcat.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] release candidate 18.05-rc3
Date: Tue, 15 May 2018 08:26:05 +0800 [thread overview]
Message-ID: <31be8f76-4f7a-7445-c3b4-c6a3620d4222@warmcat.com> (raw)
In-Reply-To: <6d3ec1fa-581d-a50e-268b-ad0605f0e65c@intel.com>
On 05/15/2018 07:18 AM, Ferruh Yigit wrote:
> A new DPDK release candidate is ready for testing:
> https://dpdk.org/browse/dpdk/tag/?id=v18.05-rc3
>
> The release notes should be complete now:
> http://dpdk.org/doc/guides/rel_notes/release_18_05.html
>
> What's new in -rc3?
> - proper runtime directory
> - consistent checks in offload API
> - compressdev API
> - Intel compressdev software driver
> - eventdev crypto adapter
> - NXP devices blacklisting
> - DPAA2 QDMA raw driver
> - DPAA2 Command Interface raw driver
> - Intel FPGA bus
> - BPF
>
> Some planned features are postponed to 18.08:
> - Hyper-V bus and NetVSC driver
> - TAP TSO
> - testpmd simulation of noisy host
>
> It is a big release candidate (322 patches),
> but next one is expected to include only some bug fixes,
> tooling or documentation updates.
>
> Everybody is tired by this release which lasts too long.
> So let's try to minimize new risks in order to close it soon.
I appreciate my first series around buildability of dpdk under gcc8 got
in, thanks for the support and assistance.
The series "GCC8 fixes against lagopus" fixes dpdk api headers so you
can actually build things against dpdk with gcc 8. Today then dpdk
itself builds cleanly under gcc 8, but when you try to build another app
against it with the same compiler, that app can't build cleanly due to
problems specifically in dpdk exported api headers. These don't show up
during dpdk build but when you actually try to use it.
I understand this stuff is really busy and difficult to manage, life
will go on for me if it gets in later, although you can't build eg
lagopus with gcc8 as it is. Lagopus has its own problems with gcc 8 but
today they target 18.02 dpdk. It will be helpful to them and others if
they can target unchanged 18.05 dpdk tag in their dpdk submodule and
then only need patches on their side (which I am preparing) for a clean
gcc8 experience.
-Andy
> We can target to make -rc4, -rc5 and finally release on 25th of May.
>
> As usual, please test this release candidate as much as you can,
> and check for possible behaviour or performance regressions.
>
> There are some open bugs to check in bugzilla:
> https://dpdk.org/tracker/buglist.cgi?bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=IN_PROGRESS&product=DPDK
>
> Thank you everyone
>
>
>
prev parent reply other threads:[~2018-05-15 0:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2233576.Okp3jBAIYA@xps>
2018-05-14 23:18 ` [dpdk-dev] [dpdk-announce] " Ferruh Yigit
2018-05-14 23:24 ` Stephen Hemminger
2018-05-14 23:31 ` Thomas Monjalon
2018-05-15 0:26 ` Andy Green [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=31be8f76-4f7a-7445-c3b4-c6a3620d4222@warmcat.com \
--to=andy@warmcat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
/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).