From: Md Rayhanul Islam <r97yhan@gmail.com>
To: dev@dpdk.org
Subject: [RFC PATCH 0/2] per-device DMA properties, with igb as the first user
Date: Fri, 2 Oct 2026 16:09:25 -0400 [thread overview]
Message-ID: <20261002200927.6235-1-r97yhan@gmail.com> (raw)
In-Reply-To: <20260918225045.177125-1-r97yhan@gmail.com>
This RFC reworks the BCM2711 DMA fix around a per-device DMA context and
an EAL sync API, after the feedback on the first posting [1].
On Raspberry Pi 4 / Compute Module 4 the PCIe host bridge translates DMA
addresses and is not cache coherent, so a device such as the Intel I210
cannot DMA at all without both being handled.
What changed since the first posting:
* The translation and the coherency are read per device from its own
bridge, not kept as one process-wide offset. EAL no longer rewrites
IOVAs; the driver translates where it programs the hardware.
* A driver opts in with RTE_PCI_DRV_DMA_NONCOHERENT, and the bus refuses
such a device to any driver that has not. That replaces the refusal
written into em by hand.
* The cache maintenance is an experimental EAL interface with explicit
directions, and the loops end in DSB SY.
* Completion comes from the Done bits, not the head register.
* Both environment variables are gone.
Tested between two Compute Module 4 boards with Intel I210s, both running
this series: testpmd txonly holds 1.42 Mpps with 64-byte frames, and a
512 MB UDP transfer with DPDK at both ends arrives byte-identical. Built
with GCC and with clang 14 -Werror.
[1] https://inbox.dpdk.org/dev/20260918225045.177125-1-r97yhan@gmail.com/
Md Rayhanul Islam (2):
eal/pci: add per-device DMA translation and synchronization
net/e1000: support non-coherent DMA
.mailmap | 1 +
doc/guides/rel_notes/release_26_11.rst | 20 ++
drivers/bus/pci/bus_pci_driver.h | 2 +
drivers/bus/pci/linux/pci.c | 6 +
drivers/bus/pci/linux/pci_dma_ranges.c | 168 ++++++++++
drivers/bus/pci/linux/pci_init.h | 2 +
drivers/bus/pci/meson.build | 1 +
drivers/bus/pci/pci_common.c | 17 +
drivers/bus/pci/private.h | 2 +
drivers/bus/pci/rte_bus_pci.h | 52 ++++
drivers/net/intel/e1000/e1000_ethdev.h | 19 ++
drivers/net/intel/e1000/igb_ethdev.c | 9 +-
drivers/net/intel/e1000/igb_rxtx.c | 409 +++++++++++++++++++++++--
lib/eal/include/meson.build | 1 +
lib/eal/include/rte_mem_sync.h | 133 ++++++++
15 files changed, 815 insertions(+), 27 deletions(-)
create mode 100644 drivers/bus/pci/linux/pci_dma_ranges.c
create mode 100644 lib/eal/include/rte_mem_sync.h
--
2.34.1
next prev parent reply other threads:[~2026-10-03 8:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 22:50 [PATCH 0/2] make PCIe DMA work on Broadcom BCM2711 Md Rayhanul Islam
2026-09-18 22:50 ` [PATCH 1/2] eal/linux: apply PCIe inbound DMA translation Md Rayhanul Islam
2026-09-18 22:50 ` [PATCH 2/2] net/e1000: maintain caches on non-coherent DMA Md Rayhanul Islam
2026-09-19 21:05 ` [PATCH 0/2] make PCIe DMA work on Broadcom BCM2711 Stephen Hemminger
2026-09-21 8:56 ` Bruce Richardson
2026-09-21 15:42 ` Stephen Hemminger
2026-09-24 19:22 ` Md Rayhanul Islam
2026-10-02 20:09 ` Md Rayhanul Islam [this message]
2026-10-02 20:09 ` [RFC PATCH 1/2] eal/pci: add per-device DMA translation and synchronization Md Rayhanul Islam
2026-10-02 20:09 ` [RFC PATCH 2/2] net/e1000: support non-coherent DMA Md Rayhanul Islam
2026-10-03 16:51 ` [RFC PATCH 0/2] per-device DMA properties, with igb as the first user Stephen Hemminger
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=20261002200927.6235-1-r97yhan@gmail.com \
--to=r97yhan@gmail.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