DPDK patches and discussions
 help / color / mirror / Atom feed
From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: "dev@dpdk.org" <dev@dpdk.org>,
	"thomas@monjalon.net" <thomas@monjalon.net>,
	"david.marchand@redhat.com" <david.marchand@redhat.com>
Cc: Song Zhu <Song.Zhu@arm.com>, Ruifeng Wang <Ruifeng.Wang@arm.com>,
	nd <nd@arm.com>,
	Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
	nd <nd@arm.com>
Subject: [dpdk-dev] Arm roadmap for 20.08
Date: Mon, 8 Jun 2020 23:16:52 +0000	[thread overview]
Message-ID: <DB6PR0802MB22165D4207A18EA377A58D8198850@DB6PR0802MB2216.eurprd08.prod.outlook.com> (raw)

(Bcc: Arm internal stake holders)

Hello,
	Following are the work items planned for 20.08:

1) LPM integration with RCU
2) rte_bitops APIs
3) rte_atomic API deprecation with-in DPDK
4) Use C11 atomic semantics in mbuf, eventdev, eal interrupts
5) Change IO barriers to align with other-multi-copy atomicity memory model for Armv8-a (DSB to DMB change)
6) CPU frequency calculation using generic counter

Thank you,
Honnappa

                 reply	other threads:[~2020-06-08 23:17 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=DB6PR0802MB22165D4207A18EA377A58D8198850@DB6PR0802MB2216.eurprd08.prod.outlook.com \
    --to=honnappa.nagarahalli@arm.com \
    --cc=Ruifeng.Wang@arm.com \
    --cc=Song.Zhu@arm.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=nd@arm.com \
    --cc=thomas@monjalon.net \
    /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).