e0477b34d9
The code in setup_dma_device has become rather convoluted, move all of
this to the drivers. Drives now pass in a DMA capable struct device which
will be used to setup DMA, or drivers must fully configure the ibdev for
DMA and pass in NULL.
Other than setting the masks in rvt all drivers were doing this already
anyhow.
mthca, mlx4 and mlx5 were already setting up maximum DMA segment size for
DMA based on their hardweare limits in:
__mthca_init_one()
dma_set_max_seg_size (1G)
__mlx4_init_one()
dma_set_max_seg_size (1G)
mlx5_pci_init()
set_dma_caps()
dma_set_max_seg_size (2G)
Other non software drivers (except usnic) were extended to UINT_MAX [1, 2]
instead of 2G as was before.
[1] https://lore.kernel.org/linux-rdma/20200924114940.GE9475@nvidia.com/
[2] https://lore.kernel.org/linux-rdma/20200924114940.GE9475@nvidia.com/
Link: https://lore.kernel.org/r/20201008082752.275846-1-leon@kernel.org
Link: https://lore.kernel.org/r/6b2ed339933d066622d5715903870676d8cc523a.1602590106.git.mchehab+huawei@kernel.org
Suggested-by: Christoph Hellwig <hch@infradead.org>
Signed-off-by: Parav Pandit <parav@nvidia.com>
Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
|
||
|---|---|---|
| .. | ||
| Kconfig | ||
| Makefile | ||
| mthca_allocator.c | ||
| mthca_av.c | ||
| mthca_catas.c | ||
| mthca_cmd.c | ||
| mthca_cmd.h | ||
| mthca_config_reg.h | ||
| mthca_cq.c | ||
| mthca_dev.h | ||
| mthca_doorbell.h | ||
| mthca_eq.c | ||
| mthca_mad.c | ||
| mthca_main.c | ||
| mthca_mcg.c | ||
| mthca_memfree.c | ||
| mthca_memfree.h | ||
| mthca_mr.c | ||
| mthca_pd.c | ||
| mthca_profile.c | ||
| mthca_profile.h | ||
| mthca_provider.c | ||
| mthca_provider.h | ||
| mthca_qp.c | ||
| mthca_reset.c | ||
| mthca_srq.c | ||
| mthca_uar.c | ||
| mthca_wqe.h | ||