From: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] 18.05 intel Roadmap
Date: Thu, 22 Feb 2018 09:22:21 +0000 [thread overview]
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BAA4AD1C46@IRSMSX108.ger.corp.intel.com> (raw)
Now that the 18.02 release is complete, we need to update the 18.05 roadmap. These are the features that we plan to contribute:
vHost Selective Data Path: Provide support for a selective datapath in the vhost-user library. The default datapath will be the existing software implementation. Alternative data paths can be added to support acceleration for virtio-compatible devices.
IFC VF Driver: A new Intel device driver for accelerated virtio data path leveraging the selective datapath support in the vhost-user library.
vHost Interrupt Mode: Add support for interrupt mode to vhost. This can be used during low traffic periods to save power or to allow the CPU to be used for other tasks.
Virtio-User Server Mode: Currently, in a container environment if the vhost-user backend restarts there's no way for it to reconnect to virtio-user. To address this, support for server mode will be added. In this mode the socket file is created by virtio-user, which the backend then connects to. This means that if the backend restarts, it can reconnect to virtio-user and continue communications.
Virtio Crypto: Support for virtio-crypto will be added to the vhost-user library. A new sample application will also be created which wil run in the host and will handle crypto requests sent by the guest.
Ethdev API to Query Recommended Descriptor Ring Sizes: Provide an ethdev API to allow applications to query the recommended descriptor ring sizes for a NIC port. The value returned should depend on the speed of the port (10G, 40G etc.) and the number of queues configured.
Memory Subsystem Improvements: Continue redesign of memory system to make DPDK less "greedy" and more suitable for use in container/cloud native environments. Specific changes include: provide ability to scale up/down memory usage at run time, provide the ability to register/unregister non-DPDK-owned hugepages with VFIO.
IP Pipeline Usability Enhancements: Improve usability of the IP Pipeline by: provide an API to add pipeline configuration profiles after initialization, refactor the IP Pipeline into separate libraries to facilitate reuse.
Compression: Provide a new compressdev API to support hardware and software acceleration of compression/decompression. A PMD for a software implementation using the Intel(r) Storage Acceleration Library will be provided.
Tunnel API: A new API will be created to manage tunnel end points, including hardware acceleration for tunnel encap/decap.
Port Representor: A port representor is a virtual PMD which provides a logical representation of any port, either physical or host-facing, on a multi-port port device. This logical port provides a mechanism for control and monitoring. The primary purpose of port representors in DPDK is to support the configuration, management and monitoring of virtual functions of a network interface. A data path will also be supported which will allow physical ports to be presented as separate logical ports within an application.
Support PPPoE/PPPoL2TPv2 in I40E PMD: Support for PPPoE and PPPoL2TPv2 will be added to the I40E PMD.
Update Intel PMDs for Rx/Tx Offload API. Intel PMDs will be updated to use the new Rx/Tx offload API.
Add Uevent Support for Hotplug: The uevent mechanism will be used to monitor the hotplug status of a device. This will allow an application to detect when a device has been added or removed.
reply other threads:[~2018-02-22 9:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=26FA93C7ED1EAA44AB77D62FBE1D27BAA4AD1C46@IRSMSX108.ger.corp.intel.com \
--to=tim.odriscoll@intel.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 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).