DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Patel, Rashmin N" <rashmin.n.patel@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] DPDK 2.2 roadmap
Date: Wed, 9 Sep 2015 17:48:44 +0000	[thread overview]
Message-ID: <C68F1134885B32458704E1E4DA3E34F34265B3F5@FMSMSX105.amr.corp.intel.com> (raw)
In-Reply-To: <1882381.9qlZTmz9zB@xps13>

There were two line items on the 2.2 roadmap: Xen Driver and Hyper-V Driver. Can you provide some more details?

Thanks,
Rashmin

-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon
Sent: Wednesday, September 09, 2015 1:45 AM
To: dev@dpdk.org
Subject: [dpdk-dev] DPDK 2.2 roadmap

Hello,

The new features for the release 2.2 must be first submitted before 2nd October.
They should be integrated before 23rd October.

In order to ease cooperation and integration, it would be nice to see announces or technical details of planned features for 2.2 or 2.3.
Then the roadmap page will be filled accordingly:
	http://dpdk.org/dev/roadmap
Generally speaking, it helps to know what you are working on and what is the status.

Thanks

  parent reply	other threads:[~2015-09-09 17:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-09  8:44 Thomas Monjalon
2015-09-09 12:56 ` O'Driscoll, Tim
2015-09-10 12:43   ` Thomas Monjalon
2015-09-10 13:26     ` Thomas F Herbert
2015-09-10 19:27     ` Flavio Leitner
2015-09-10 19:55       ` Thomas Monjalon
2015-09-11  1:23         ` Yuanhan Liu
2015-09-11  8:08     ` O'Driscoll, Tim
2015-09-14  8:40     ` Zhang, Helin
2015-09-14  8:57       ` Thomas Monjalon
2015-09-15 20:11         ` Olga Shern
2015-09-09 17:48 ` Patel, Rashmin N [this message]
2015-09-09 18:00   ` Stephen Hemminger
2015-09-15  9:16 ` David Marchand
2015-09-14 13:44 Matej Vido
2015-09-14 14:02 ` Thomas Monjalon
2015-09-14 15:37   ` Matej Vido

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=C68F1134885B32458704E1E4DA3E34F34265B3F5@FMSMSX105.amr.corp.intel.com \
    --to=rashmin.n.patel@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).