DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maayan Kashani <mkashani@nvidia.com>
To: dpdk-dev <dev@dpdk.org>
Subject: NVIDIA roadmap for 25.07
Date: Mon, 14 Apr 2025 18:17:34 +0000	[thread overview]
Message-ID: <PH7PR12MB701859C1E93151C53A25762AB2B32@PH7PR12MB7018.namprd12.prod.outlook.com> (raw)
In-Reply-To: <PH7SPRMB0021912A0C7A7B4238F0C2DDB20C2@PH7SPRMB0021.namprd12.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 1906 bytes --]

Please find below NVIDIA roadmap for 25.07 release:

EAL change
=============
Improve PCI device string comparisons by using bus-specific parsing functions.
Ensure consistent handling of PCI device numbers, regardless of the format used by comparing the parsed PCI
address instances instead of the string representations.

Net/mlx5 PMD updates  
=====================  

  1.  Tx datapath optimization
Optimize Tx datapath performance by changing Tx inner buffers allocation and alignment in memory.

  1.  Memory statistics visibility for debugging
                Adding new xstats counters for debugging memory usage and allocations.

  1.  Support for legacy rte_flow (non-template) on top of the async hardware mechanism (HWS)
has been added as a beta feature, serving as a preview for future NICs (e.g., ConnectX-9+),
where legacy rte_flow will no longer be supported,
and will be exchanged with the [already available] template async interface.
While this mode is compatible with older NICs (prior to ConnectX-9),
it is not recommended since existing legacy mode delivers better performance.
Developers are strongly encouraged to transition to the template API for both
superior performance and access to an enhanced feature set.

  1.  Handle SF/VF representor removal in DPDK (supported with ConnectX-6DX and above)
Listen to the kernel events and remove needed SFs/VFs representors.

  1.  Cross Numa support
Enable fallback to any socket to support cross NUMA memory allocations during initialization.

  1.  Support matching on IPv6 frag extension header with rte_flow template API.

  1.  Support RTE_FLOW_ACTION_TYPE_COUNT on group 0 (root) in rte_flow template API.

  1.  Support IP-in-IP matching in rte_flow template API.

Doc
=======
Updated mlx5 documentation with feature description and usage examples.


Regards,
Maayan Kashani

[-- Attachment #2: Type: text/html, Size: 13776 bytes --]

      reply	other threads:[~2025-04-14 18:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-25 14:52 NVIDIA roadmap for 25.03 Maayan Kashani
2025-04-14 18:17 ` Maayan Kashani [this message]

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=PH7PR12MB701859C1E93151C53A25762AB2B32@PH7PR12MB7018.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).