From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: web@dpdk.org, John Mcnamara <john.mcnamara@intel.com>,
Tim O'Driscoll <tim.odriscoll@intel.com>
Subject: [dpdk-web] [PATCH] update Intel roadmap for 19.08
Date: Thu, 13 Jun 2019 14:11:31 +0100 [thread overview]
Message-ID: <20190613131131.72126-1-ferruh.yigit@intel.com> (raw)
Intel roadmap is announced in the dpdk-dev mailing list:
https://mails.dpdk.org/archives/dev/2019-May/132609.html
Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
---
Cc: John Mcnamara <john.mcnamara@intel.com>
Cc: Tim O'Driscoll <tim.odriscoll@intel.com>
---
content/roadmap/_index.md | 14 ++++++++++++--
1 file changed, 12 insertions(+), 2 deletions(-)
diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
index 7244044..d25626f 100644
--- a/content/roadmap/_index.md
+++ b/content/roadmap/_index.md
@@ -16,8 +16,18 @@ This list is obviously neither complete nor guaranteed.
- TCP SEQ and ACK offload with rte_flow API and mlx5 implementation
- ICMP ping offload with rte_flow API and mlx5 implementation
- initial support for Huawei Intelligent PCIe NIC
-
-### Version 19.11 (2019 September) {#1911}
+- ice PMD rte_flow, ethertype & tunnel filters and inner L3/L4 checksum strip/insertion support
+- i40e PMD partial offload support
+- rawdev IOAT (Intel QuickData Technology) PMD
+- af_xdp PMD busy polling and zero copy (using external mbuf) support
+- bbdev new 4G FEC PMD & add 5G FEC extension support
+- power telemetry busyness report support
+- cryptodev encrypted digest for 5G use-cases support
+- cryptodev RSA API update
+- sched library enhancements
+- IPsec fragmented/multi-segment packets support
+
+### Version 19.11 (2019 November) {#1911}
### Nice to have - Future {#future}
----
--
2.21.0
next reply other threads:[~2019-06-13 13:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 13:11 Ferruh Yigit [this message]
2019-06-25 13:54 ` 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=20190613131131.72126-1-ferruh.yigit@intel.com \
--to=ferruh.yigit@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).