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 24.11
Date: Sun, 25 Aug 2024 11:58:39 +0000	[thread overview]
Message-ID: <PH7PR12MB9223D719E610E430E8F5CD0DB28A2@PH7PR12MB9223.namprd12.prod.outlook.com> (raw)

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

Please find below NVIDIA roadmap for 24.11 release:

A. rte_flow new APIs 
================= 

  1.  New action - Jump to a table index
Jump to a table index directly without doing the hash inside the matcher to improve the performance by reducing hops.
This feature enables distribution based on various fields, not subject to RSS only fields.

B. Net/mlx5 PMD updates 
===================== 

  1.  Optimize FDB domain tables​ 
Reduce the duplication of Tx / Rx tables in the FDB domain to optimize the performance and reduce memory
usage to allow room for more offloads (increase total scale). 

  1.  Hairpin statistics query​ 
Support per queue hairpin related counters, Rx miss, Tx error and queue drop, etc.​ 
This will provide more visibility for debug, telemetry, and monitoring purposes to the users​. 
This feature is supported from CX7/BF3 and above and on the VF. For CX6-Dx it supports port level stats and PF.

  1.  RTE FLOW backward compatible API​ 
Support RTE FLOW non-template API on top of template async API.  
Strating from ConnectX-8 NIC and BlueField-4 DPU,  RTE FLOW non-template API will not be supported.
This feature will allow the non-template API to be supported with template mode for interim
application translation and with functional template mode limitations.

  1.  Report detail reason of HWS rule insertion failure​
Provide detailed failure reason to the upper layer, e.g. table full, hash conflict, input error​​.
The application can handle based on the failures.​​
  
C. Test apps updates   
=================  

  1.  Support the changes in rte_flow listed above in testpmd.  

  1.  Support hairpin with 4 physical ports in testpmd. 
For Nic’s supporting more than dual ports, adjust the hairpin logic to allow use of all ports.  
Current testpmd only allows consecutive pair for hairpin.
This feature is intended to allow use of any pair. 


Regards,
Maayan Kashani


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

                 reply	other threads:[~2024-08-25 11:58 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=PH7PR12MB9223D719E610E430E8F5CD0DB28A2@PH7PR12MB9223.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).