DPDK patches and discussions
 help / color / mirror / Atom feed
From: Lior Margalit <lmargalit@nvidia.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: NVIDIA roadmap for 22.07
Date: Tue, 3 May 2022 10:48:40 +0000	[thread overview]
Message-ID: <BY5PR12MB5512E9508C8FDF220CDC938FCDC09@BY5PR12MB5512.namprd12.prod.outlook.com> (raw)

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

Please find below NVIDIA roadmap for 22.07 release:

rte_flow new APIs:
===============
[1] Add port flags for pre-configuration flow hints.
[RFC,1/2] ethdev: port flags for pre-configuration flow hints.
Introduce a flag to specify if the operations on each flow will be executed on the same queue.
[2] Get aged-out flows of a given port and flow queue.
[RFC,2/2] ethdev: queue-based flow aged report
Supported when the port is configured with the above flag to strict the flow operations to the same queue.
[3] Support IPv4/IPv6 ECN in MODIFY_FIELD action.
[v1,1/4] ethdev: add IPv4/IPv6 ECN header rewrite action

Net/mlx5 PMD updates:
====================
[1] Support the rte_flow changes listed above.
[2] Support switch granularity rule matching.
To reduce the number of rules with matching on the source vport, and simplify the operations when adding or removing VMs, allow the application to create the represented_port item with empty spec and mask as matching pattern, to filter traffic from all vports in a single flow rule.
[3] Support Meter Policy with MODIFY_FIELD action in green/yellow action.
[4] Control traffic from host port to wire port.
Introduce LWM (limit watermark) attribute for RX queue to send event to the dpdk app when RX queue fullness reach the LWM limit.
[5] Expand the global per-device MR cache dynamically.
Support the case where the app is using mempools in external memory with more than the initial cache capacity (512 chunks).
[6] Enabling SPI based hashing for ESP
When using RSS on ESP packets, hashing may not be efficient, because the fields used by the hash functions are only the outer IPs, so adding the SPI hash field can extend the spreading of IPSec packets.
[7] Support for template API and asynchronous queue-based management.
The rte_flow enhancements were integrated in 22.03.
Add local cache of Counter objects per queue.

Vdpa/mlx5 PMD updates:
=====================
[1] Add vDPA multi-threads infra to reduce the migration time.

Crypto/mlx5 PMD updates:
======================
[1] Support crypto operations with the plaintext import method.
In plaintext mode, there is no need to login with credential devarg in order to enable crypto operations in the device.

Testpmd updates:
===============
[1] Support the changes in rte_flow listed above.


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

                 reply	other threads:[~2022-05-03 10:48 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=BY5PR12MB5512E9508C8FDF220CDC938FCDC09@BY5PR12MB5512.namprd12.prod.outlook.com \
    --to=lmargalit@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).