All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ruifeng Wang <Ruifeng.Wang@arm.com>
To: "thomas@monjalon.net" <thomas@monjalon.net>,
	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>,  nd <nd@arm.com>,
	nd <nd@arm.com>
Subject: Re: [dpdk-dev] Arm roadmap for 21.11
Date: Wed, 22 Sep 2021 08:15:05 +0000	[thread overview]
Message-ID: <AS8PR08MB708016CFF9AB32106A80DFA99EA29@AS8PR08MB7080.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <2509537.JPC37jZjU7@thomas>

> -----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.

> 


  reply	other threads:[~2021-09-22  8:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-11 22:01 [dpdk-dev] Arm roadmap for 21.11 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 [this message]
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=AS8PR08MB708016CFF9AB32106A80DFA99EA29@AS8PR08MB7080.eurprd08.prod.outlook.com \
    --to=ruifeng.wang@arm.com \
    --cc=Honnappa.Nagarahalli@arm.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=nd@arm.com \
    --cc=pbhagavatula@marvell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.