DPDK patches and discussions
 help / color / mirror / Atom feed
From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "Song Zhu (Arm Technology China)" <Song.Zhu@arm.com>,
	Pravin Kantak <Pravin.Kantak@arm.com>,
	Philippe Robin <Philippe.Robin@arm.com>, nd <nd@arm.com>,
	nd <nd@arm.com>
Subject: [dpdk-dev] Arm's roadmap for 19.11
Date: Wed, 28 Aug 2019 04:06:28 +0000	[thread overview]
Message-ID: <VE1PR08MB51498A4F22383A443FE32AA598A30@VE1PR08MB5149.eurprd08.prod.outlook.com> (raw)

Hello,
	Following are the work items planned for 19.11 release:

1) Integrate WFE/SEV instructions in spinlock and ring library
2) Add support for lock-free stack mempool handler
3) Integrate LPM and Hash libraries with RCU
4) Enable lock-free data path algorithms in L3-Fwd application
5) Template based rte_ring APIs to support custom ring element sizes
6) Use C11 atomic built-in APIs in mem-if driver
7) Performance optimizations in i40e and ixgbe 
8) Enable N1 Server Development Platform config

Thank you,
Honnappa

                 reply	other threads:[~2019-08-28  4:06 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=VE1PR08MB51498A4F22383A443FE32AA598A30@VE1PR08MB5149.eurprd08.prod.outlook.com \
    --to=honnappa.nagarahalli@arm.com \
    --cc=Philippe.Robin@arm.com \
    --cc=Pravin.Kantak@arm.com \
    --cc=Song.Zhu@arm.com \
    --cc=dev@dpdk.org \
    --cc=nd@arm.com \
    /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).