DPDK patches and discussions
 help / color / mirror / Atom feed
From: Tetsuya Mukawa <mukawa@igel.co.jp>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] deadline notice
Date: Thu, 11 Jun 2015 18:20:58 +0900	[thread overview]
Message-ID: <557952FA.1020708@igel.co.jp> (raw)
In-Reply-To: <17955759.q268rHF4cX@xps13>

On 2015/06/11 17:34, Thomas Monjalon wrote:
> 2015-06-11 10:30, Tetsuya Mukawa:
>> On 2015/06/11 3:39, Thomas Monjalon wrote:
>>> 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,
>>
>> Please add "BSD Port Hotplug Support".
>> http://dpdk.org/dev/patchwork/project/dpdk/list/?submitter=64&state=new
> It was not reported because they are mostly some reworks.
> But you're right, hotplug in BSD is a feature.

Thanks!

Tetsuya

  reply	other threads:[~2015-06-11  9:21 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 [this message]
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
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=557952FA.1020708@igel.co.jp \
    --to=mukawa@igel.co.jp \
    --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).