DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: announce@dpdk.org
Subject: DPDK 26.07 released
Date: Wed, 22 Jul 2026 22:13:57 +0200	[thread overview]
Message-ID: <nkvYuCbUTBKN7caG89ssLw@monjalon.net> (raw)

A new major release is available:
	https://fast.dpdk.org/rel/dpdk-26.07.tar.xz

It was a small release cycle:
	868 commits from 132 authors
	1388 files changed, 99644 insertions(+), 21594 deletions(-)

It is not planned to start a maintenance branch for 26.07.
This version is ABI-compatible with 25.11.

Highlights of 26.07:
	- option --pagesz-mem for per-page-size maximum
	- option --no-auto-probing for no device at init
	- less mempool cache misses in run-to-completion
	- peek style API for staged-ordered ring
	- RISC-V vector paths
	- PTP helpers and clock relay example
	- selective Rx API to save PCI bandwidth
	- vhost memory hotplug
	- pcap driver enhanced
	- LinkData sxe2 NIC driver
	- extended BPF API and hardened validator
	- real-time telemetry watcher
	- AI review helpers

Important note:
	Applications may need to retune their mempool cache size
	after upgrading to DPDK 26.07.

More details in the release notes:
	https://doc.dpdk.org/guides/rel_notes/release_26_07.html


There are 49 new contributors (including authors, reviewers and testers).
Welcome Adam Hassick, Alexey Simakov, Alok Mishra, Andrea Panattoni,
Arin Kharkar, Borys Tsyrulnikov, Chengfei Han, Chenna Arnoori,
Claudia Cauli, Dakota Sicher, Daniil Agalakov, Daniil Iskhakov,
Daphne Priscilla, Dawid Wesierski, Deepthi Kavalur, Denis Lyulin,
Denis Sergeev, Gena Tertychnyi, James Raphael Tiovalen, Jay Wang,
Jie Liu, Kavya AV, Koushik Bhargav Nimoji, Linhu Li, Marcel Telka,
Marek Kasiewicz, Mark Blasko, Mateusz Fryze, Matthew Gee, Maxime Peim,
Md Shofiqul Islam, Michal Sieron, Mukul Katiyar, Ouyang Hao,
Pratik Senapati, Pravin M Bathija, Raghavendra Ningoji, Rayane Boussanni,
Samyak Jain, Shuzo Ichiyoshi, Siraj Luthfi Ananda, Sushmita Hoskeri,
Weijun Pan, Wenqiang Chen, Ye Chen, Zhiguang Jin, Zijian Li,
Zoe Cheimets, and Zongyu Wu.

Below are the top commit counts per employer (with authors count):
	230     Intel (27)
	136     stephen@networkplumber.org (1)
	 62     NVIDIA (8)
	 60     Red Hat (3)
	 54     Marvell (18)
	 48     Huawei (7)
	 32     LinkData (1)
	 31     Free (2)
	 27     Trustnet (1)
	 27     NXP (5)
	 25     Broadcom (8)
	 21     Google (4)
	 14     UNH (3)
	 12     Microsoft (4)
	 10     SmartShare Systems (1)

A big thank to all courageous people who took on the non rewarding task
of reviewing other's job.
Based on Reviewed-by and Acked-by tags, the top non-PMD reviewers are:
     72     Bruce Richardson <bruce.richardson@intel.com>
     48     Konstantin Ananyev <konstantin.ananyev@huawei.com>
     41     Chengwen Feng <fengchengwen@huawei.com>
     24     Stephen Hemminger <stephen@networkplumber.org>


The next release will be 26.11 in November.
New features may be submitted during August:
	http://core.dpdk.org/roadmap#dates

Enjoy the summer!

Thanks everyone



                 reply	other threads:[~2026-07-22 20:14 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=nkvYuCbUTBKN7caG89ssLw@monjalon.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox