From: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
To: web@dpdk.org
Cc: nd@arm.com, honnappa.nagarahalli@arm.com
Subject: [dpdk-web] [PATCH] update Arm roadmap for 20.05
Date: Tue, 10 Mar 2020 18:49:18 +0000 [thread overview]
Message-ID: <20200310184918.15511-1-honnappa.nagarahalli@arm.com> (raw)
Signed-off-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
---
content/roadmap/_index.md | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
index 6f3d6b6..693f3c5 100644
--- a/content/roadmap/_index.md
+++ b/content/roadmap/_index.md
@@ -18,6 +18,10 @@ This list is obviously neither complete nor guaranteed.
- additional crypto algorithms in Nitrox PMD
- regexdev
- UBSan in build
+- Use of C11 __atomic APIs in timer library, service core feature and
+ VirtIO split ring feature
+- Performance optimizations in i40e and mlx drivers for Arm platforms
+- RCU API for deferred resource reclamation
### Nice to have - Future {#future}
----
--
2.17.1
next reply other threads:[~2020-03-10 18:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 18:49 Honnappa Nagarahalli [this message]
2020-03-29 20:57 ` 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=20200310184918.15511-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).