From: Maayan Kashani <mkashani@nvidia.com>
To: dpdk-dev <dev@dpdk.org>
Subject: NVIDIA roadmap for 25.03
Date: Wed, 25 Dec 2024 14:52:50 +0000 [thread overview]
Message-ID: <PH7SPRMB0021912A0C7A7B4238F0C2DDB20C2@PH7SPRMB0021.namprd12.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2437 bytes --]
Please find below NVIDIA roadmap for 25.03 release:
EAL change
=============
Improve PCI device string comparisons by using bus-specific parsing functions.
By comparing the parsed PCI address instances instead of the string representations,
the application can ensure consistent handling of PCI device numbers, regardless of the format used.
rte_ethdev new APIs
=================
Hairpin Queue Statistics query
Track detailed statistics for hairpin operations at the queue level, including counters on receive misses, transmission errors, and queue drops.
This enhanced monitoring capability enables improved debugging, telemetry collection, and performance tracking.
Hardware support and capabilities:
* ConnectX-6 Dx: Statistics available at port level and Physical Function (PF).
* ConnectX-7, BlueField-3 and newer: Extended support for per-queue statistics and Virtual Function (VF) monitoring.
Net/mlx5 PMD updates
=====================
1. Forwarding Database (FDB) domain tables Optimization
Network flows in FDB often lack directional indicators,
resulting in redundant flow entries created in both receive (Rx) and transmit (Tx) domains.
This has been changed with the introduction of a unified FDB approach which addresses the inefficiency.
Therefore, the unified FDB reduces the duplication of Tx / Rx tables in the FDB domain ,
optimize the performance and reduce memory usage to allow room for more offloads (increase total scale).
1. Optimization of device probing time
Probing time with hundreds of REPs is too long, this optimization is cashing the probing data and using a new kernel API.
1. Support eCPRI matching in template API.
Support eCPRI based on Flex Parser
1. Support queue and RSS actions from FDB
Save the hops in Rx direction for performance, bypass NIC Rx domain
1. Memory pool debuggability
Introducing live tracing at multiple log levels for operations within the ipool, providing detailed visibility into its internal structures and processes.
This feature also includes checks for double malloc/free operations to enhance reliability and debuggability.
Test apps updates
=================
Support the changes in rte_flow listed above in testpmd.
Regards,
Maayan Kashani
[-- Attachment #2: Type: text/html, Size: 16334 bytes --]
reply other threads:[~2024-12-25 14:53 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=PH7SPRMB0021912A0C7A7B4238F0C2DDB20C2@PH7SPRMB0021.namprd12.prod.outlook.com \
--to=mkashani@nvidia.com \
--cc=dev@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;
as well as URLs for NNTP newsgroup(s).