DPDK website maintenance
 help / color / mirror / Atom feed
From: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
To: thomas@monjalon.net
Cc: web@dpdk.org, Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
Subject: [dpdk-web] [PATCH] Add Arm's roadmap for 19.11
Date: Tue, 27 Aug 2019 23:15:37 -0500	[thread overview]
Message-ID: <20190828041537.18020-1-honnappa.nagarahalli@arm.com> (raw)

Add Arm's roadmap for 19.11

Signed-off-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
---
 content/roadmap/_index.md | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
index ebac14f..32d4715 100644
--- a/content/roadmap/_index.md
+++ b/content/roadmap/_index.md
@@ -13,6 +13,14 @@ This list is obviously neither complete nor guaranteed.
 
 - Rx metadata in mbuf, with rte_flow API and mlx5 implementation
 - hairpin forwarding offload, with mlx5 implementation
+- Performance optimizations in i40e and ixgbe PMDs for Arm platforms
+- Add N1 Server Development Platform config
+- Use C11 atomic built-in functions in mem-if driver
+- Integrate WFE/SEV instructions in spinlock and ring library
+- Add support for lock-free stack mempool handler
+- Integrate RCU library with LPM and Hash libraries
+- Template based rte_ring APIs to support custom ring element sizes
+- Enable lock-free data path algorithms in L3-Fwd application
 
 ### Nice to have - Future {#future}
 ----
-- 
2.17.1


             reply	other threads:[~2019-08-28  4:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-28  4:15 Honnappa Nagarahalli [this message]
2019-09-11 14:02 ` 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=20190828041537.18020-1-honnappa.nagarahalli@arm.com \
    --to=honnappa.nagarahalli@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).