From: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
To: web@dpdk.org, thomas@monjalon.net, honnappa.nagarahalli@arm.com
Cc: nd@arm.com
Subject: [dpdk-web] [PATCH v2] update Arm roadmap for 20.08
Date: Wed, 10 Jun 2020 00:38:30 +0000 [thread overview]
Message-ID: <20200610003830.5155-1-honnappa.nagarahalli@arm.com> (raw)
Roadmap was announced in the dpdk-dev mailing list:
http://mails.dpdk.org/archives/dev/2020-June/169542.html
Signed-off-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
---
content/roadmap/_index.md | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
index 4dd7b3e..b4a259e 100644
--- a/content/roadmap/_index.md
+++ b/content/roadmap/_index.md
@@ -13,6 +13,11 @@ This list is obviously neither complete nor guaranteed.
- flow action object API
- flow sampling and mirroring API
+- Bit operations APIs for PMDs
+- Use C11 atomic semantics in mbuf, eventdev, eal interrupts
+- CPU frequency calculation using generic counter for Arm platforms
+- Integrate RCU library with LPM library
+- Change IO barriers to use 'DMB' instruction for Armv8-a
- performance optimizations in mlx drivers for Arm platforms
- mlx5 memory management options, and queue stop/start
- mlx5 eCPRI matching and Tx scheduling for 5G
@@ -32,7 +37,7 @@ This list is obviously neither complete nor guaranteed.
### Nice to have - Future {#future}
----
-- integrate RCU deferred resource reclamation API with LPM and hash libraries
+- integrate RCU deferred resource reclamation API with hash library
- lock-free l3fwd algorithms
- multi-process rework
- automatic UIO/VFIO binding
--
2.17.1
next reply other threads:[~2020-06-10 0:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 0:38 Honnappa Nagarahalli [this message]
2020-06-10 7:45 ` 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=20200610003830.5155-1-honnappa.nagarahalli@arm.com \
--to=honnappa.nagarahalli@arm.com \
--cc=nd@arm.com \
--cc=thomas@monjalon.net \
--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).