From: Thomas F Herbert <therbert@redhat.com>
To: dev@dpdk.org
Subject: Re: DPDK 2.2 roadmap
Date: Thu, 10 Sep 2015 09:26:53 -0400 [thread overview]
Message-ID: <55F1851D.8010402@redhat.com> (raw)
In-Reply-To: <2207263.dDyMmkz5Pr@xps13>
On 9/10/15 8:43 AM, Thomas Monjalon wrote:
> 2015-09-09 12:56, O'Driscoll, Tim:
>> DCB for i40e &X550: DCB support will be extended to the i40e and X550 NICs.
> A patch for DCB on X550 is already applied but the release notes part was forgotten.
>
>> IPsec Sample App: A sample application will be provided to show how the
>> cryptodev library can be used to implement IPsec. This will be based on
>> the NetBSD IPsec implementation.
> For each API, it is really interesting to have some unit tests and some
> examples to show how it should be used. However adding an IPsec stack looks
> to be beyond the need of an API example. It may be big and difficult to
> maintain when updating DPDK.
> Why not spawn a new project here: http://dpdk.org/browse/ ?
>
>> Refactor EAL for Non-PCI Devices: This has been discussed extensively on the mailing list. See the RFCs for Refactor eal driver registration code (http://dpdk.org/ml/archives/dev/2015-September/023257.html) and Remove pci driver from vdevs (http://dpdk.org/ml/archives/dev/2015-August/023016.html).
> I have the feeling we should think it as an unification work to reduce
> differences between physical and virtual devices handling.
> Probably it will have to be continued during 2.3 cycle.
>
>> Vhost Multi-Queue Support: The vhost-user library will be updated to provide multi-queue support in the host similar to the RSS model so that guest driver may allocate multiple rx/tx queues which then may be used to load balance between cores. See http://dpdk.org/ml/archives/dev/2015-August/022758.html for more details.
> Does it require a patch on Qemu?
I believe it requires V6 of the Qemu patch. Changchun or fbl can confirm
this. Reference to where to acquire the Qemu patch is documented in the
multiqueue patch here:
http://dpdk.org/ml/archives/dev/2015-August/022758.html
>
>> Config Granularity of RSS for i40e: All RSS hash and filter configurations for IPv4/v6, TCP/UDP, GRE, etc will be implemented for i40e. This includes support for QinQ and tunneled packets.
> What is missing in i40e RSS/filtering?
>
>> I40e 32-bit GRE Keys: Both 24 and 32 bit keys for GRE will be supported for i40e.
> Could you please give more details?
>
>> X550 Enhancements: Support VF TSO, more Entries in RSS and per VF RSS, network overlay support with flow director for X550.
> Could you please give more details on "network overlay support with flow director"?
>
> Thanks for sharing your plan
>
>
>
> --
> Thomas F Herbert Red Hat
next prev parent reply other threads:[~2015-09-10 13:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-09 8:44 DPDK 2.2 roadmap 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 [this message]
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
2015-09-09 18:00 ` Stephen Hemminger
2015-09-15 9:16 ` David Marchand
-- strict thread matches above, loose matches on Subject: below --
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=55F1851D.8010402@redhat.com \
--to=therbert@redhat.com \
--cc=dev@dpdk.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.