(Bcc: Arm internal stake holders) Hello, Following are the work items planned for 21.11: 1) New rte_wait_until_xxx APIs and their use in various libraries 2) Meson build changes to pick Arm architecture features based on compiler support availability. 3) C11 atomic built-ins in app/test and examples. 4) Simplify implementation of rte_ctrl_thread_create. 5) Ensure EAL remote launch and EAL wait for lcore APIs provide the correct memory ordering guarantees. 6) Fix i40e PMD Rx descriptor read ordering issues. Please let me know if there are any questions. Thank you, Honnappa
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?
What about the old item "Arm CRC32 in generic API"?
<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. > > 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/
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?
> -----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: http://patches.dpdk.org/project/dpdk/cover/20210902053253.3017858-1-feifei.wang2@arm.com/ 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] http://patches.dpdk.org/project/dpdk/patch/20200512204015.1963-1- > pbhagavatula@marvell.com/ > > Should we keep this item in the roadmap? @Pavan Nikhilesh Bhagavatula to confirm if this is still on plan. >
>> -----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. >>