CONFIG_DPAA_ERRATUM_A050385:

General informations

The Linux kernel configuration item CONFIG_DPAA_ERRATUM_A050385:

• prompt:
• type: bool
• depends on: CONFIG_ARM64 && CONFIG_FSL_DPAA
• defined in drivers/net/ethernet/freescale/fman/Kconfig
• found in Linux kernels: 5.6–5.19, 6.0–6.8, 6.9-rc+HEAD

Help text

DPAA FMan erratum A050385 software workaround implementation: align buffers, data start, SG fragment length to avoid FMan DMA splits. FMAN DMA read or writes under heavy traffic load may cause FMAN internal resource leak thus stopping further packet processing. The FMAN internal queue can overflow when FMAN splits single read or write transactions into multiple smaller transactions such that more than 17 AXI transactions are in flight from FMAN to interconnect. When the FMAN internal queue overflows, it can stall further packet processing. The issue can occur with any one of the following three conditions: 1. FMAN AXI transaction crosses 4K address boundary (Errata A010022) 2. FMAN DMA address for an AXI transaction is not 16 byte aligned, i.e. the last 4 bits of an address are non-zero 3. Scatter Gather (SG) frames have more than one SG buffer in the SG list and any one of the buffers, except the last buffer in the SG list has data size that is not a multiple of 16 bytes, i.e., other than 16, 32, 48, 64, etc. With any one of the above three conditions present, there is likelihood of stalled FMAN packet processing, especially under stress with multiple ports injecting line-rate traffic.

Hardware

LKDDb

Raw data from LKDDb:

• (none)

Sources

This page is automaticly generated with free (libre, open) software lkddb(see lkddb-sources).

The data is retrived from:

• Linux kernel
• Linux Kernel Driver DataBase (LKDDb)

Automatic links from Google (and ads)

Custom Search

Popular queries: