From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: "dev@dpdk.org" <dev@dpdk.org>,
"thomas@monjalon.net" <thomas@monjalon.net>,
David Cunado <David.Cunado@arm.com>
Cc: Ruifeng Wang <Ruifeng.Wang@arm.com>,
Wathsala Wathawana Vithanage <wathsala.vithanage@arm.com>,
Lijian Zhang <Lijian.Zhang@arm.com>, nd <nd@arm.com>,
nd <nd@arm.com>
Subject: Arm's roadmap for 23.07
Date: Tue, 16 May 2023 04:01:51 +0000 [thread overview]
Message-ID: <DBAPR08MB5814B075558BBE372BA9D2EB98799@DBAPR08MB5814.eurprd08.prod.outlook.com> (raw)
(Bcc: Arm internal stake holders)
Hello,
Following are the work items planned for 23.07:
1. Buffer recycle (a.k.a direct-rearm of Rx side buffers) APIs and implementation.
2. Zero-copy mempool APIs, integration with i40e PMD and test cases.
3. Remove rte_ring generic implementation and improve c11 implementation (to allow for moving to C11 atomic APIs).
4. QAT on ARM support announcement.
5. IPSecMB support for tag SECLIB-IPSEC-2023.3.21.
Thank you,
Honnappa
reply other threads:[~2023-05-16 4:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=DBAPR08MB5814B075558BBE372BA9D2EB98799@DBAPR08MB5814.eurprd08.prod.outlook.com \
--to=honnappa.nagarahalli@arm.com \
--cc=David.Cunado@arm.com \
--cc=Lijian.Zhang@arm.com \
--cc=Ruifeng.Wang@arm.com \
--cc=dev@dpdk.org \
--cc=nd@arm.com \
--cc=thomas@monjalon.net \
--cc=wathsala.vithanage@arm.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).