From: Thomas Monjalon <thomas@monjalon.net>
To: announce@dpdk.org
Subject: [dpdk-dev] [dpdk-announce] release candidate 21.11-rc1
Date: Mon, 25 Oct 2021 23:40:38 +0200 [thread overview]
Message-ID: <2318225.2c2R9pzSo5@thomas> (raw)
A new DPDK release candidate is ready for testing:
https://git.dpdk.org/dpdk/tag/?id=v21.11-rc1
There are 1171 new patches in this snapshot, big as expected.
Release notes:
https://doc.dpdk.org/guides/rel_notes/release_21_11.html
Highlights of 21.11-rc1:
* General
- more than 512 MSI-X interrupts
- hugetlbfs subdirectories
- mempool flag for non-IO usages
- device class for DMA accelerators
- DMA drivers for Intel DSA and IOAT
* Networking
- MTU handling rework
- get all MAC addresses of a port
- RSS based on L3/L4 checksum fields
- flow match on L2TPv2 and PPP
- flow flex parser for custom header
- control delivery of HW Rx metadata
- transfer flows API rework
- shared Rx queue
- Windows support of Intel e1000, ixgbe and iavf
- testpmd multi-process
- pcapng library and dumpcap tool
* API/ABI
- API namespace improvements (mempool, mbuf, ethdev)
- API internals hidden (intr, ethdev, security, cryptodev, eventdev, cmdline)
- flags check for future ABI compatibility (memzone, mbuf, mempool)
Please test and report issues on bugs.dpdk.org.
DPDK 21.11-rc2 is expected in two weeks or less.
Thank you everyone
next reply other threads:[~2021-10-25 21:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-25 21:40 Thomas Monjalon [this message]
2021-10-28 7:10 ` [dpdk-dev] [dpdk-announce] release candidate 21.11-rc1 Jiang, YuX
2021-11-01 11:53 ` Jiang, YuX
2021-11-05 21:51 ` Thinh Tran
2021-11-08 10:50 ` Pei Zhang
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=2318225.2c2R9pzSo5@thomas \
--to=thomas@monjalon.net \
--cc=announce@dpdk.org \
/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.