From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "Devlin, Michelle" <michelle.devlin@intel.com>
Subject: Intel roadmap for 22.07
Date: Thu, 24 Mar 2022 08:32:45 +0000 [thread overview]
Message-ID: <DM6PR11MB3227A9AB8898F6B741A1E9E8FC199@DM6PR11MB3227.namprd11.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1232 bytes --]
The following are the proposed Intel roadmap items for DPDK 22.07:
* dmadev library add telemetry support
* pipeline connection tracking improvements
* pipeline packet mirroring support
* pipeline hash support
* pipeline default action arguments
* ethdev library add protocol-based header split API
* ice PMD add header split support
* ice PMD implement rte_tm to support 3 level QoS
* EEPROM info dump add telemetric command
* iavf PMD add raw pattern rte_flow support
* iavf PMD add Rx timestamp offload support
* Intel IPU SoC add new "idpf" PMD
* openssl PMD add OpenSSL 3.0 lib support
* QAT PMD remove deprecated dependency on openssl 1.x
* QAT Gen 4 add asymmetric crypto algorithm support
* AESNI-MB PMD support chained mbuf for AES GCM and chachapoly
* vhost add async dequeue support for split ring
* vhost add small copy with CPU in DSA accelerated vhost
* Add thread-unsafe/thread-safe in-flight packets check
* DLB allow assignment of SW/HW credit quanta assignment on port usage hint
* DLB allow dlb2 eventdev apps to use specific COS on per port basis
* DLB add support for DLB 2.5 QE weight hardware feature
* bbdev new PMD for Intel ACC101 device
* add eventdev_dump sample application
[-- Attachment #2: Type: text/html, Size: 4967 bytes --]
next reply other threads:[~2022-03-24 8:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 8:32 Mcnamara, John [this message]
2022-03-29 12:15 ` Intel roadmap for 22.07 Thomas Monjalon
2022-03-29 15:13 ` Chautru, Nicolas
2022-03-29 18:51 ` Thomas Monjalon
2023-07-31 14:12 ` Thomas Monjalon
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=DM6PR11MB3227A9AB8898F6B741A1E9E8FC199@DM6PR11MB3227.namprd11.prod.outlook.com \
--to=john.mcnamara@intel.com \
--cc=dev@dpdk.org \
--cc=michelle.devlin@intel.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 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.