DPDK patches and discussions
 help / color / mirror / Atom feed
From: Gagandeep Singh <G.Singh@nxp.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: NXP roadmap for 24.11
Date: Tue, 27 Aug 2024 05:27:45 +0000	[thread overview]
Message-ID: <PAXPR04MB82052E6353FCD25CB4CAB331E1942@PAXPR04MB8205.eurprd04.prod.outlook.com> (raw)

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

Hi,

Please find below roadmap of NXP for 24.11 release:

bus/fslmc:
========
                Upgrade MC firmware to 10.39 for DPAA2 platform. Latest MC version with general bug fixes, TM issue fix for >8 queues, and API enhancements for flow distribution statistics.

net/dpaa2:
=========
      - Flow APIs implementation enhancement and bug fixes.

net/dpaa:
========
    - IEEE1588 support
               The DPAA driver supports IEEE1588 (Precision Time Protocol) for precise clock synchronization.
    -  OH port support
               Introducing Offline (O/H) port support, enabling hardware-based packet processing and loopback capabilities. This feature allows for efficient packet exchange between applications, leveraging two queues for receive and send operations. With a maximum speed of 3.75 Mpps (2.5 Gbps), O/H ports facilitate communication between applications, enabling use cases like inter-process communication and packet processing.

net/eQoS:
========
               The eQoS Ethernet Driver is a new DPDK driver proposed for the 24.11 release, supporting NXP's i.MX8MP, i.MX8DXL, i.MX91, and i.MX93 platforms.

net/enetc:
========
     - support new ethernet enetc4 driver version4 of existing Enetc driver on NXP i.MX95 platform, featuring:
* Virtual Functions (VFs) for virtualized environments
          * VF-PF messaging for enhanced feature control
* Multiple queues with RSS-based distribution for optimized network performance

net/enetfec:
==========
                Improves enetfec driver with:

- Coverity bug fixes, addressing potential security vulnerabilities
- Datapath logic fixes to resolve non-cache coherent platform issues

crypto/dpaax:
===========
                - Improves crypto/dpaax functionality with:

- Fixes for PDCP descriptors, ensuring accurate data processing
- Debugging enhancements for easier issue identification and resolution
- Memory leak fixes, preventing resource waste and ensuring stability
- optimizations

These enhancements improve the reliability, stability, performance and debuggability of crypto on dpaax platforms.

dma/dpaax:
==========
                Complete overhaul of the DMA driver code for DPAA1 and DPAA2 platforms, focusing on:

- Simplified code structure for improved maintainability
- Enhanced readability for easier understanding and debugging
- Future-proof design for seamless integration of upcoming features

Apart from that:

  *   Enhances the memory dump in proc-info application.
  *   Enhances the l3fwd application for route rules.
  *   Suggestions and fixes some meson related options related to installation directories, binaries and source code.

Regards,
Gagan


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

                 reply	other threads:[~2024-08-27  5:27 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=PAXPR04MB82052E6353FCD25CB4CAB331E1942@PAXPR04MB8205.eurprd04.prod.outlook.com \
    --to=g.singh@nxp.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).