DPDK website maintenance
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: web@dpdk.org
Cc: humin29@huawei.com, fengchengwen@huawei.com
Subject: [PATCH] update Huawei roadmap for 22.03
Date: Mon, 10 Jan 2022 09:47:45 +0100	[thread overview]
Message-ID: <20220110084745.14050-1-thomas@monjalon.net> (raw)

Was announced in the dpdk-dev mailing list:
https://mails.dpdk.org/archives/dev/2022-January/232091.html

Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---
 content/roadmap/_index.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
index abe7576..457b948 100644
--- a/content/roadmap/_index.md
+++ b/content/roadmap/_index.md
@@ -15,6 +15,8 @@ This list is obviously neither complete nor guaranteed.
 - allow hugepage reuse at startup
 - Arm CRC32 in generic API
 <!-- Networking -->
+- ethdev queue info dump API
+- ethdev private info API
 - flow template API
 - flow management queue API
 - Tx QoS marking API
@@ -39,6 +41,7 @@ This list is obviously neither complete nor guaranteed.
 - vhost library statistics
 - virtio hash reporting
 <!-- Network apps -->
+- more info in dpdk-proc-info
 <!-- Crypto -->
 - qat async crypto
 - qat with OpenSSL-3.0 library
@@ -47,6 +50,7 @@ This list is obviously neither complete nor guaranteed.
 - event vector support in SW Rx eventdev adapter
 - control adapter and RX adapter enhancements in DLB driver
 <!-- Others -->
+- hisilicon DMA engine for Kunpeng 930
 
 ### Nice to have - Future {#future}
 ----
-- 
2.34.1


                 reply	other threads:[~2022-01-10  8:47 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=20220110084745.14050-1-thomas@monjalon.net \
    --to=thomas@monjalon.net \
    --cc=fengchengwen@huawei.com \
    --cc=humin29@huawei.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).