From: "Mattias Rönnblom" <mattias.ronnblom@ericsson.com>
To: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
"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>, Gavin Hu <Gavin.Hu@arm.com>,
Jeff Brownlee <Jeff.Brownlee@arm.com>,
Philippe Robin <Philippe.Robin@arm.com>,
Pravin Kantak <Pravin.Kantak@arm.com>, nd <nd@arm.com>
Subject: Re: [dpdk-dev] Arm roadmap for 20.05
Date: Wed, 11 Mar 2020 08:25:51 +0000 [thread overview]
Message-ID: <aa8476af-d916-28c5-2538-105a6949abc8@ericsson.com> (raw)
In-Reply-To: <VE1PR08MB514950F91289D7882BDDA2E198FF0@VE1PR08MB5149.eurprd08.prod.outlook.com>
On 2020-03-10 17:42, Honnappa Nagarahalli wrote:
> Hello,
> Following are the work items planned for 20.05:
>
> 1) Use C11 atomic APIs in timer library
> 2) Use C11 atomic APIs in service cores
> 3) Use C11 atomics in VirtIO split ring
> 4) Performance optimizations in i40e and MLX drivers for Arm platforms
> 5) RCU defer API
> 6) Enable Travis CI with no huge-page tests - ~25 test cases
>
> Thank you,
> Honnappa
Maybe you should have a look at legacy DPDK atomics as well? Avoiding a
full barrier for the add operation, for example.
next prev parent reply other threads:[~2020-03-11 8:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 16:42 Honnappa Nagarahalli
2020-03-11 8:25 ` Mattias Rönnblom [this message]
2020-03-20 20:45 ` Honnappa Nagarahalli
2020-03-21 8:17 ` Mattias Rönnblom
2020-03-21 8:23 ` Mattias Rönnblom
2020-03-23 17:14 ` Honnappa Nagarahalli
2020-03-23 17:34 ` Mattias Rönnblom
2020-03-24 8:01 ` Morten Brørup
2020-03-24 18:53 ` Honnappa Nagarahalli
2020-03-24 21:41 ` Honnappa Nagarahalli
2020-04-07 5:15 ` Honnappa Nagarahalli
2020-04-09 1:25 ` Chen, Zhaoyan
2020-04-07 19:10 ` Mattias Rönnblom
2020-03-23 17:12 ` 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=aa8476af-d916-28c5-2538-105a6949abc8@ericsson.com \
--to=mattias.ronnblom@ericsson.com \
--cc=Gavin.Hu@arm.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Jeff.Brownlee@arm.com \
--cc=Philippe.Robin@arm.com \
--cc=Pravin.Kantak@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).