DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Iremonger, Bernard" <bernard.iremonger@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] deadline notice
Date: Thu, 11 Jun 2015 09:30:50 +0000	[thread overview]
Message-ID: <8CEF83825BEC744B83065625E567D7C204A2E521@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <2520130.3p9lvqUWmZ@xps13>

> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> Sent: Wednesday, June 10, 2015 7:40 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] deadline notice
> 
> Hi,
> 
> As described in the roadmap (http://dpdk.org/dev/roadmap), starting from
> this week, every new feature submission will be postponed to release 2.2.
> The below features, which were submitted earlier, will be accepted in the
> release 2.1 if they are correctly reviewed and acknowledged before the end
> of June.
> New fixes and needed reworks will be accepted, of course.
> During July, only important and small fixes will be integrated.
> 
> Planned features for DPDK 2.1:
> 	- memory size without hugepage
> 	- indirect mbuf cloning
> 	- packet type
> 	- memzone freeing
> 	- interrupt mode
> 	- speed capability
> 	- IEEE1588 timestamping
> 	- multicast filtering
> 	- flow director extension
> 	- ethtool-like ops
> 	- hash key size
> 	- ring hotplug
> 	- e1000 hotplug
> 	- igbvf allmulticast
> 	- ixgbe base update
> 	- ixgbe hotplug
> 	- ixgbe LRO
> 	- ixgbe extended stats
> 	- i40e base update
> 	- i40e hotplug
> 	- i40e port mirroring
> 	- i40e QinQ
> 	- fm10k hotplug
> 	- fm10k promiscuous
> 	- fm10k mac vlan filtering
> 	- mlx4 update
> 	- cxgbe driver
> 	- bnx2x driver
> 	- Hyper-V driver
> 	- Xen driver
> 	- vmxnet3 vlan filtering
> 	- vmxnet3 jumbo
> 	- virtio hotplug
> 	- vhost multiqueue
> 	- vhost migration
> 	- pcap jumbo
> 	- bonding hotplug
> 	- bonding dynamic RSS
> 	- bonding mode 4 external state machine
> 	- uio MSI-X
> 	- TILE-Gx architecture
> 	- HTM lock elision for x86
> 	- OSv support
> 	- jhash update
> 	- toeplitz hash
> 	- cuckoo hash
> 	- KNI optimization
> 	- KNI multicast
> 	- packet framework enhancements
> 	- cmdline polling mode
> 	- proc_info app
> 	- VXLAN example
> 
> Thanks a lot

Hi Thomas,

The following patch was submitted on 10th March 2015, but does not seem to be on   DPDK patchwork.

[dpdk-dev] [RFC] af_packet: support port hotplug

Regards,

Bernard.

  parent reply	other threads:[~2015-06-11  9:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-10 18:39 Thomas Monjalon
2015-06-10 21:13 ` Abdul, Jaffar
2015-06-11 14:00   ` Thomas Monjalon
2015-06-11  1:30 ` Tetsuya Mukawa
2015-06-11  8:34   ` Thomas Monjalon
2015-06-11  9:20     ` Tetsuya Mukawa
2015-06-11  7:27 ` Simon Kagstrom
2015-06-11  8:33   ` Thomas Monjalon
2015-06-11  8:45     ` Simon Kagstrom
2015-06-11  9:30 ` Iremonger, Bernard [this message]
2015-06-11  9:58   ` Thomas Monjalon
2015-06-11 10:04     ` Iremonger, Bernard
2015-06-11 11:39       ` Thomas Monjalon

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=8CEF83825BEC744B83065625E567D7C204A2E521@IRSMSX108.ger.corp.intel.com \
    --to=bernard.iremonger@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).