From: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
To: Ruifeng Wang <Ruifeng.Wang@arm.com>,
"thomas@monjalon.net" <thomas@monjalon.net>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
David Marchand <david.marchand@redhat.com>, nd <nd@arm.com>,
nd <nd@arm.com>
Subject: Re: [dpdk-dev] Arm roadmap for 21.11
Date: Wed, 22 Sep 2021 08:17:58 +0000 [thread overview]
Message-ID: <PH0PR18MB4086EA297CCC6CAD437F7727DEA29@PH0PR18MB4086.namprd18.prod.outlook.com> (raw)
In-Reply-To: <AS8PR08MB708016CFF9AB32106A80DFA99EA29@AS8PR08MB7080.eurprd08.prod.outlook.com>
>> -----Original Message-----
>> From: Thomas Monjalon <thomas@monjalon.net>
>> Sent: Wednesday, September 22, 2021 3:27 PM
>> To: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>; Pavan
>> Nikhilesh Bhagavatula <pbhagavatula@marvell.com>;
>jerinj@marvell.com
>> Cc: 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
>>
>> 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?
>
>RFC posted at:
>https://urldefense.proofpoint.com/v2/url?u=http-
>3A__patches.dpdk.org_project_dpdk_cover_20210902053253.3017858-
>2D1-2Dfeifei.wang2-
>40arm.com_&d=DwIFAg&c=nKjWec2b6R0mOyPaz7xtfQ&r=1cjuAHrGh7
>45jHNmj2fD85sUMIJ2IPIDsIJzo6FN6Z0&m=467uW7OBS2WzGwSBOg1g1
>kJtexO_IyEUPgJvPd_Mvg0&s=TXbJ1eg3WeJUy9yQpsKJ53yYwlLtpxywU
>wlo0WGEh0o&e=
>Working on a re-spin to get the API more generic.
>
>>
>> > > What about the old item "Arm CRC32 in generic API"?
>> > This one is from Marvell [1]
>> > + Pavan from Marvell
>> > >
>> > [1] https://urldefense.proofpoint.com/v2/url?u=http-
>3A__patches.dpdk.org_project_dpdk_patch_20200512204015.1963-
>2D1-
>2D&d=DwIFAg&c=nKjWec2b6R0mOyPaz7xtfQ&r=1cjuAHrGh745jHNmj2
>fD85sUMIJ2IPIDsIJzo6FN6Z0&m=467uW7OBS2WzGwSBOg1g1kJtexO_Iy
>EUPgJvPd_Mvg0&s=qLjtO8f1aziI8BHSf91WEce-pP2Ouz--
>XId3d0YyHRM&e=
>> pbhagavatula@marvell.com/
>>
>> Should we keep this item in the roadmap?
>
>@Pavan Nikhilesh Bhagavatula to confirm if this is still on plan.
>
I don't have cycles for this in September, will see if I can take it up in
October. I believe RC1 deadline is around October 15.
If ARM wants to take over the patch I'm fine with that too.
Thanks,
Pavan.
>>
prev parent reply other threads:[~2021-09-22 8:18 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
2021-09-22 8:15 ` Ruifeng Wang
2021-09-22 8:17 ` Pavan Nikhilesh Bhagavatula [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=PH0PR18MB4086EA297CCC6CAD437F7727DEA29@PH0PR18MB4086.namprd18.prod.outlook.com \
--to=pbhagavatula@marvell.com \
--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=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).