RFC devmem/io_uring: Allow devices without parent PCI device
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest4 patches 19 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | net: Allow non parent devices to be used for ZC DMAinclude/ | +13 | 19 replies | |
| 2/4 | io_uring/zcrx: Use the new netdev_get_dma_dev() APIio_uring/ | +1 | 0 replies | |
| 3/4 | net: devmem: Use the new netdev_get_dma_dev() APInet/ | +9 | 0 replies | |
| 4/4 | net/mlx5e: Enable HDS zerocopy flows for SFsdrivers/ | +3 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC net-next 0/4] devmem/io_uring: Allow devices without parent PCI device
The io_uring and devmem code is assuming that the parent device of the netdev is a DMA capable device. This is not always the case.
Some devices do have a DMA capable device that can be used, but not as
parent: mlx5 SFs have an auxdev as parent, but they do have an associated PCI device.
Also, if DMA is not supported the operation should be blocked. Otherwise the mapping will return success with 0 mapped entries and the caller will consider the mapping as succesful.
This RFC is supposed to start the discussion on the best way to:
- Block the binding operation early if not supported.
- Allow devices that support this usecase but don't have a parent device as a PCI device.
Dragos Tatulea (4):
net: Allow non parent devices to be used for ZC DMA io_uring/zcrx: Use the new netdev_get_dma_dev() API
net: devmem: Use the new netdev_get_dma_dev() API net/mlx5e: Enable HDS zerocopy flows for SFs
drivers/net/ethernet/mellanox/mlx5/core/en_main.c | 3 +++ include/linux/netdevice.h | 13 +++++++++++++ io_uring/zcrx.c | 2 +- net/core/devmem.c | 10 +++++++++- 4 files changed, 26 insertions(+), 2 deletions(-)
Signature · 1 line
2.50.0