From: Thomas Monjalon <thomas@monjalon.net>
To: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
Cc: web@dpdk.org, nd@arm.com
Subject: Re: [dpdk-web] [PATCH] update Arm roadmap for 20.08
Date: Tue, 09 Jun 2020 10:08:03 +0200 [thread overview]
Message-ID: <2523689.0iaz9iMqiZ@thomas> (raw)
In-Reply-To: <20200609032823.22469-1-honnappa.nagarahalli@arm.com>
09/06/2020 05:28, Honnappa Nagarahalli:
> Signed-off-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
Additional explanation:
Was announced in the dpdk-dev mailing list:
http://mails.dpdk.org/archives/dev/2020-June/169542.html
> +- Bit operations APIs for PMDs
> +- rte_atomic API deprecation with-in DPDK
Deprecation is not a feature to coordinate in the roadmap I think.
> +- Use C11 atomic semantics in mbuf, eventdev, eal interrupts
> +- CPU frequency calculation using generic counter for Arm platforms
> +- LPM library integration with RCU library
I would word it in reverse order: isn't it the RCU lib which is integrated in LPM?
> +- Change IO barriers to align with other-multi-copy atomicity memory model for Armv8-a
I don't understand "other-multi-copy atomicity".
next prev parent reply other threads:[~2020-06-09 8:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 3:28 Honnappa Nagarahalli
2020-06-09 8:08 ` Thomas Monjalon [this message]
2020-06-09 15:54 ` Honnappa Nagarahalli
2020-06-09 17:31 ` 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=2523689.0iaz9iMqiZ@thomas \
--to=thomas@monjalon.net \
--cc=honnappa.nagarahalli@arm.com \
--cc=nd@arm.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).