From: Thomas Monjalon <thomas@monjalon.net>
To: web@dpdk.org
Cc: honnappa.nagarahalli@arm.com
Subject: [PATCH] update Arm roadmap for 24.03
Date: Tue, 6 Feb 2024 22:39:37 +0100 [thread overview]
Message-ID: <20240206213937.180009-1-thomas@monjalon.net> (raw)
Was announced in the dpdk-dev mailing list:
http://mails.dpdk.org/archives/dev/2024-February/286408.html
Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---
content/roadmap/_index.md | 2 ++
1 file changed, 2 insertions(+)
diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
index 5b249a9..6317862 100644
--- a/content/roadmap/_index.md
+++ b/content/roadmap/_index.md
@@ -17,10 +17,12 @@ This list is obviously neither complete nor guaranteed.
- non-temporal memory copy
- mempool cache zero-copy get/put bulk
- memarea library
+- pointer compression
- ring generic implementation removal and C11 improvement
- PMU counter for self monitoring/profiling
- VFIO cdev/iommufd
- UACCE bus
+- hash bulk key lookup with SVE
<!-- DMA -->
- dmadev trace points in data path
<!-- Networking -->
--
2.43.0
reply other threads:[~2024-02-06 21:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240206213937.180009-1-thomas@monjalon.net \
--to=thomas@monjalon.net \
--cc=honnappa.nagarahalli@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).