DPDK website maintenance
 help / color / mirror / Atom feed
From: Marko Kovacevic <marko.kovacevic@intel.com>
To: web@dpdk.org
Cc: john.mcnamara@intel.com, tim.odriscoll@intel.com,
	thomas@monjalon.net, Marko Kovacevic <marko.kovacevic@intel.com>
Subject: [dpdk-web] [PATCH] update Intel roadmap for 19.05
Date: Fri, 15 Feb 2019 16:43:37 +0000	[thread overview]
Message-ID: <20190215164337.38535-1-marko.kovacevic@intel.com> (raw)

Intel roadmap is announced in the dpdk-dev mailing list:
http://mails.dpdk.org/archives/dev/2019-February/124766.html

Signed-off-by: Marko Kovacevic <marko.kovacevic@intel.com>
---
 content/roadmap/_index.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
index ccfcb63..a587b56 100644
--- a/content/roadmap/_index.md
+++ b/content/roadmap/_index.md
@@ -24,6 +24,12 @@ This list is obviously neither complete nor guaranteed.
 - mlx5 out of the box performance improvements
 - mlx5/mlx4 robustness improvement for Rx/Tx errors
 - failsafe support in multi-process
+- QAT asymmetric crypto with support for modexp and modinv
+- QAT compression PMD support for large scatter-gather lists
+- add a DPDK PMD to support AF_XDP
+- support for additional crypto/auth algorithms in the ipsec library
+- initial support for DPDK on Windows
+- add new baseband device turbo PMD
 
 ### Version 19.08 (2019 August) {#1908}
 
-- 
2.9.5

             reply	other threads:[~2019-02-15 16:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-15 16:43 Marko Kovacevic [this message]
2019-02-15 21:05 ` Thomas Monjalon
2019-02-18 12:30   ` Mcnamara, John
2019-02-18 14:51     ` 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=20190215164337.38535-1-marko.kovacevic@intel.com \
    --to=marko.kovacevic@intel.com \
    --cc=john.mcnamara@intel.com \
    --cc=thomas@monjalon.net \
    --cc=tim.odriscoll@intel.com \
    --cc=web@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).