From: Thomas Monjalon <thomas@monjalon.net>
To: web@dpdk.org
Cc: honnappa.nagarahalli@arm.com
Subject: [PATCH] update Arm roadmap for 22.03
Date: Mon, 10 Jan 2022 09:52:33 +0100 [thread overview]
Message-ID: <20220110085233.14425-1-thomas@monjalon.net> (raw)
Was announced in the dpdk-dev mailing list:
https://mails.dpdk.org/archives/dev/2022-January/232134.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 457b948..3fb2009 100644
--- a/content/roadmap/_index.md
+++ b/content/roadmap/_index.md
@@ -13,12 +13,14 @@ This list is obviously neither complete nor guaranteed.
<!-- General -->
- allow hugepage reuse at startup
+- index-based per core mempool cache
- Arm CRC32 in generic API
<!-- Networking -->
- ethdev queue info dump API
- ethdev private info API
- flow template API
- flow management queue API
+- direct-rearm of Rx side buffers
- Tx QoS marking API
- VLAN-based input color metering
- IP reassembly offload
--
2.34.1
next reply other threads:[~2022-01-10 8:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 8:52 Thomas Monjalon [this message]
2022-01-10 14:41 ` Honnappa Nagarahalli
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=20220110085233.14425-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).