From: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
To: web@dpdk.org
Cc: honnappa.nagarahalli@arm.com, nd@arm.com
Subject: [dpdk-web] [PATCH] update Arm roadmap for 20.02
Date: Thu, 19 Dec 2019 21:00:04 +0000 [thread overview]
Message-ID: <20191219210004.8153-1-honnappa.nagarahalli@arm.com> (raw)
Signed-off-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
---
content/roadmap/_index.md | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
index ed727f0..771ddc6 100644
--- a/content/roadmap/_index.md
+++ b/content/roadmap/_index.md
@@ -12,18 +12,20 @@ This list is obviously neither complete nor guaranteed.
### Version 20.02 (2020 February) {#2002}
- rte_flow actions for mirroring and multicast
-- Arm WFE/SEV instructions in spinlock and ring library
-- integrate RCU library with LPM and hash libraries
-- lock-free l3fwd algorithms
+- AArch64 crypto library integration with Armv8 crypto PMD
+- Arm WFE/SEV instructions in ticket lock
- eventdev examples in l3fwd and ipsec-secgw
- OCTEON TX2 inline IPsec using rte_security
- rte_security improved performance for IPsec with software crypto
- regexdev
-- template based ring API
+- rte_ring API for user defined ring element size
- UBSan in build
### Nice to have - Future {#future}
----
+- RCU APIs for deferred resource reclamation
+- integrate RCU deferred resource reclamation APIs with LPM and hash libraries
+- lock-free l3fwd algorithms
- multi-process rework
- automatic UIO/VFIO binding
- infiniband driver class (ibdev)
--
2.17.1
next reply other threads:[~2019-12-19 21:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-19 21:00 Honnappa Nagarahalli [this message]
2020-01-08 22:19 ` 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=20191219210004.8153-1-honnappa.nagarahalli@arm.com \
--to=honnappa.nagarahalli@arm.com \
--cc=nd@arm.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).