From: Thomas Monjalon <thomas@monjalon.net>
To: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
Cc: "web@dpdk.org" <web@dpdk.org>, nd <nd@arm.com>
Subject: Re: [dpdk-web] [PATCH] update Arm roadmap for 20.08
Date: Tue, 09 Jun 2020 19:31:22 +0200 [thread overview]
Message-ID: <49742572.9s6HCQ56s5@thomas> (raw)
In-Reply-To: <DB6PR0802MB221618D245A2A1C1DBE8971B98820@DB6PR0802MB2216.eurprd08.prod.outlook.com>
Thanks for the replies.
Feel free to send a v2 that I can merge.
09/06/2020 17:54, Honnappa Nagarahalli:
> Thanks Thomas for your comments.
>
> > -----Original Message-----
> > From: Thomas Monjalon <thomas@monjalon.net>
> > Sent: Tuesday, June 9, 2020 3:08 AM
> > To: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
> > Cc: web@dpdk.org; nd <nd@arm.com>
> > Subject: Re: [PATCH] update Arm roadmap for 20.08
> >
> > 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.
> Ok, no problem. I just wanted to make sure that the community is on-board in reviewing the patch and making decisions. I guess the proposal on the mailing list is enough for that?
>
> >
> > > +- 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?
> I guess it is more about which library was created first. I will reverse the order.
>
> >
> > > +- Change IO barriers to align with other-multi-copy atomicity memory
> > model for Armv8-a
> >
> > I don't understand "other-multi-copy atomicity".
> There were few references provided in the patch. They are at [1], [2] and [3]. But, I guess it is not clear what this work item means exactly. I can change it as follows:
>
> "Change IO barriers to use 'DMB' instruction for Armv8-a"
>
> The patch itself is trivial. But, it is a basic change affecting all the drivers for Arm platforms. So, I would like to call out everyone's attention.
>
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=22ec71615d824f4f11d38d0e55a88d8956b7e45f
> [2] https://www.youtube.com/watch?v=i6DayghhA8Q
> [3] https://www.cl.cam.ac.uk/~pes20/armv8-mca/
>
> >
>
>
prev parent reply other threads:[~2020-06-09 17:31 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
2020-06-09 15:54 ` Honnappa Nagarahalli
2020-06-09 17:31 ` Thomas Monjalon [this message]
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=49742572.9s6HCQ56s5@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).