From: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] 19.02 Intel Roadmap
Date: Fri, 23 Nov 2018 11:11:26 +0000 [thread overview]
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BAB77C1B20@IRSMSX108.ger.corp.intel.com> (raw)
As discussed at yesterday's Release Status Meeting, we need to update our Roadmap page (http://core.dpdk.org/roadmap/) for 19.02. The features that we plan to contribute are described below. We'll submit a patch to update the roadmap page with this info.
vDPA Live Migration Software Fallback: The current vDPA library provides the vDPA driver an interface to implement hardware-based dirty page logging. A software fallback option will be added to handle situations where the hardware does not log dirty pages.
IPsec Library: An initial version of a DPDK IPsec library will be provided. This will define data structures and APIs to prepare IPsec data for crypto processing, APIs to handle ESP header encap/decap for tunnel and transport modes, and capabilities such as initialising Security Associations. The existing IPsec Security Gateway sample application (ipsec-secgw) will be updated to use the new library.
Compression Performance Test Tool: A performance test application will be created which will allow performance testing of compression PMDs.
I40E Queue Request: A new operation (VIRTCHNL_OP_REQUEST_QUEUES) will be implemented to allow an I40E VF to request a specific number of queues from the PF.
next reply other threads:[~2018-11-23 11:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-23 11:11 O'Driscoll, Tim [this message]
2018-12-02 0:17 ` Thomas Monjalon
2018-12-02 2:00 ` Stephen Hemminger
2018-12-02 6:40 ` Rami Rosen
2018-12-02 11:57 ` O'Driscoll, Tim
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=26FA93C7ED1EAA44AB77D62FBE1D27BAB77C1B20@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).