From: Thomas Monjalon <thomas@monjalon.net>
To: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>,
"jerinj@marvell.com" <jerinj@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
David Marchand <david.marchand@redhat.com>,
Ruifeng Wang <Ruifeng.Wang@arm.com>, nd <nd@arm.com>
Subject: Re: [dpdk-dev] Arm roadmap for 21.11
Date: Wed, 22 Sep 2021 09:26:48 +0200 [thread overview]
Message-ID: <2509537.JPC37jZjU7@thomas> (raw)
In-Reply-To: <DBAPR08MB58147AEB5DB8C6F85E3A304598A19@DBAPR08MB5814.eurprd08.prod.outlook.com>
22/09/2021 00:54, Honnappa Nagarahalli:
> <snip>
> > 12/09/2021 00:01, Honnappa Nagarahalli:
> > > 1) New rte_wait_until_xxx APIs and their use in various libraries
> >
> > I don't understand what it is referring to.
> > Please could you explain?
> Currently we have rte_wait_until_equal API. However this API is not applicable in cases which can involve other comparisons? We are trying to define a more generic API.
No RFC yet? So no need to add it in the roadmap for 21.11?
> > What about the old item "Arm CRC32 in generic API"?
> This one is from Marvell [1]
> + Pavan from Marvell
> >
> [1] http://patches.dpdk.org/project/dpdk/patch/20200512204015.1963-1-pbhagavatula@marvell.com/
Should we keep this item in the roadmap?
next prev parent reply other threads:[~2021-09-22 7:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-11 22:01 Honnappa Nagarahalli
2021-09-21 22:05 ` Thomas Monjalon
2021-09-21 22:54 ` Honnappa Nagarahalli
2021-09-22 7:26 ` Thomas Monjalon [this message]
2021-09-22 8:15 ` Ruifeng Wang
2021-09-22 8:17 ` Pavan Nikhilesh Bhagavatula
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=2509537.JPC37jZjU7@thomas \
--to=thomas@monjalon.net \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Ruifeng.Wang@arm.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=nd@arm.com \
--cc=pbhagavatula@marvell.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).