Re: [PATCH net-next V2 09/13] net/mlx5e: Use the correct DMA dev when data_direct is enabled

[sashiko-bot@kernel.org]

> From: Dragos Tatulea <dtatulea@nvidia.com>
> 
> When the data_direct private flag is enabled, return the data direct
> device instead of the NIC PF PCI device in .ndo_queue_get_dma_dev.
> 
> The memory provider maps the payload buffers against that device, so
> the page_pool of a data direct RQ has to use it as well. Add
> mlx5e_get_dma_dev() which returns the DMA device of an mlx5_core_dev for
> either mode and use it in both places.
> 
> Running .ndo_queue_get_dma_dev while the data direct device is going
> away returns NULL because the device pointer is already cleared.
> Opening a data direct RQ fails with -ENODEV for the same reason.
> 
> Leased queues are not supported in data-direct mode because there is
> currently no mechanism to revoke leased queues from the leaser.
> 
> Rename the dev argument to netdev because there are too many confusing
> "dev"-based names in this function.
> 
> Signed-off-by: Dragos Tatulea <dtatulea@nvidia.com>
> Reviewed-by: Cosmin Ratiu <cratiu@nvidia.com>
> Signed-off-by: Tariq Toukan <tariqt@nvidia.com>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261110183826.2927274-1-tariqt@nvidia.com?part=9