From: "Zhang, Helin" <helin.zhang@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] closing version 2.0.0-rc1
Date: Fri, 27 Feb 2015 00:42:01 +0000 [thread overview]
Message-ID: <F35DEAC7BCE34641BA9FAC6BCA4A12E70A80CCCC@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <3361041.jsZCZet79c@xps13>
Hi Thomas
For "unified packet type", it has been acked by Konstantin, and carefully reviewed by Oliver, and reviewed by Cunming, Bruce, Jingjing, etc.
The only open comment is that detailed description of each packet type should be added. I will complete it today and hopefully it can be in R2.0. Could you help to check it again and if it can be in R2.0? Thank you very much!
Regards,
Helin
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> Sent: Wednesday, February 25, 2015 5:50 AM
> To: dev@dpdk.org
> Subject: [dpdk-dev] closing version 2.0.0-rc1
>
> 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
>
> Some missing features may still be integrated in the last minute run:
> * hotplug
> * mlx4 driver
> * interrupt mode
> * sched enhancements
>
> Some other features were submitted too late or haven't been properly
> reviewed, so they are postponed (deferred state in patchwork):
> * tile arch
> * ixgbe base update
> * i40e TSO
> * xen net-front driver
> * hyper-v driver
> * bnx2x driver
> * unified packet type
>
> Thanks for your attention
prev parent reply other threads:[~2015-02-27 0:42 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
2015-02-27 0:42 ` Zhang, Helin [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=F35DEAC7BCE34641BA9FAC6BCA4A12E70A80CCCC@SHSMSX104.ccr.corp.intel.com \
--to=helin.zhang@intel.com \
--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).