From: Ruifeng Wang <Ruifeng.Wang@arm.com>
To: "thomas@monjalon.net" <thomas@monjalon.net>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
David Marchand <david.marchand@redhat.com>,
Richael Zhuang <Richael.Zhuang@arm.com>, nd <nd@arm.com>,
nd <nd@arm.com>
Subject: Re: [dpdk-dev] Arm roadmap for 21.08
Date: Wed, 30 Jun 2021 03:13:07 +0000 [thread overview]
Message-ID: <AM5PR0802MB24656A952C6F5CB9429859F59E019@AM5PR0802MB2465.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <1716338.E4ccCddWsE@thomas>
> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Tuesday, June 29, 2021 6:40 PM
> To: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
> Cc: dev@dpdk.org; David Marchand <david.marchand@redhat.com>;
> Ruifeng Wang <Ruifeng.Wang@arm.com>; Richael Zhuang
> <Richael.Zhuang@arm.com>; nd <nd@arm.com>
> Subject: Re: [dpdk-dev] Arm roadmap for 21.08
>
> 03/06/2021 06:41, Honnappa Nagarahalli:
> > Following are the work items planned for 21.08:
> >
> > 1) Add support for CPPC power driver
> > 2) i40e PMD performance improvements
> > 3) MLX5 PMD performance improvements
> > 4) C11 atomic built-ins in app/test
> > 5) l3fwd performance improvements (continued from last roadmap)
>
> Added in the online roadmap:
> https://git.dpdk.org/tools/dpdk-web/commit/?id=8c41712ac72f00
>
> > Please let me know if there are any questions.
>
> There is still this item from an older roadmap:
> - Arm CRC32 in generic API
This item should relates to:
http://patches.dpdk.org/project/dpdk/patch/20200512204015.1963-1-pbhagavatula@marvell.com/
Looks the patch needs to be updated.
>
>
prev parent reply other threads:[~2021-06-30 3:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-03 4:41 Honnappa Nagarahalli
2021-06-29 10:39 ` Thomas Monjalon
2021-06-30 3:13 ` Ruifeng Wang [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=AM5PR0802MB24656A952C6F5CB9429859F59E019@AM5PR0802MB2465.eurprd08.prod.outlook.com \
--to=ruifeng.wang@arm.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Richael.Zhuang@arm.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--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).