From: Stephen Hemminger <stephen@networkplumber.org>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] closing version 2.0.0-rc1
Date: Tue, 24 Feb 2015 16:56:40 -0800 [thread overview]
Message-ID: <20150224165640.22f15e48@urahara> (raw)
In-Reply-To: <3361041.jsZCZet79c@xps13>
On Tue, 24 Feb 2015 22:50:29 +0100
Thomas Monjalon <thomas.monjalon@6wind.com> wrote:
> It is time to close the first release candidate for DPDK 2.0.
> Then we are going to enter into the RC testing phase which was planned
> from 23rd February to 13th March. Only fixes, and cleanups will be accepted.
> At the end, the release should be out on 31st March.
>
> This is the list of the integrated features:
> * ABI versioning
> * x32 ABI
> * non-eal thread supports
> * multi-pthread per core
> * jobstats library
> * reorder library
> * acl for AVX2
> * crc hash arch-independent
> * uio_pci_generic support
> * kni optimizations
> * vhost-user support
> * virtio (link, vlan, mac, port IO, perf)
> * ixgbevf RSS
> * i40e hash filtering
> * i40e nvgre offloading
> * i40e switch
> * fm10k driver
> * bonding mode 4 tests
> * bonding mode 6
> * Rx/Tx callbacks
> * unified flow types
> * remove old filtering API (flow director, flex, ethertype, syn, ntuple)
> * remove device arguments limit
> * add indirect attached mbuf flag
> * use default port configuration in testpmd
> * tunnel offloading in testpmd
I have a bunch more fixes to vmxnet3, but they are small.
next prev parent reply other threads:[~2015-02-25 0:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 21:50 Thomas Monjalon
2015-02-25 0:56 ` Stephen Hemminger [this message]
2015-02-27 0:42 ` Zhang, Helin
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=20150224165640.22f15e48@urahara \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).