From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: "dev@dpdk.org" <dev@dpdk.org>,
"thomas@monjalon.net" <thomas@monjalon.net>,
David Marchand <david.marchand@redhat.com>
Cc: Confluence Collaboration <ConfluenceCollaboration@arm.com>,
Dhruv Tripathi <Dhruv.Tripathi@arm.com>,
Paul Szczepanek <Paul.Szczepanek@arm.com>, nd <nd@arm.com>
Subject: Arm roadmap for 24.03
Date: Mon, 5 Feb 2024 05:21:16 +0000 [thread overview]
Message-ID: <0F4A5668-D821-4F6E-A8A4-666C0F84755C@arm.com> (raw)
Hello,
Following are the patches planned for 24.03 release.
1) Pointer compression APIs
https://patchwork.dpdk.org/project/dpdk/list/?series=30100
2) Add SVE support for hash bulk key lookup
https://patchwork.dpdk.org/project/dpdk/list/?series=30183
3) Add support for Neoverse V2
https://patchwork.dpdk.org/project/dpdk/list/?series=30831
4) Configuration changes for cross build
https://patchwork.dpdk.org/project/dpdk/list/?series=30448
5) RCU library fixes
https://patchwork.dpdk.org/project/dpdk/list/?series=31000
Thank you,
Honnappa
reply other threads:[~2024-02-05 5:21 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=0F4A5668-D821-4F6E-A8A4-666C0F84755C@arm.com \
--to=honnappa.nagarahalli@arm.com \
--cc=ConfluenceCollaboration@arm.com \
--cc=Dhruv.Tripathi@arm.com \
--cc=Paul.Szczepanek@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).