Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1561064 > unrolled thread

Re: [PATCH v2 00/26] IB: Optimize DMA mapping

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: [PATCH v2 00/26] IB: Optimize DMA mapping Jason Gunthorpe <jgunthorpe@obsidianresearch.com> - 2017-01-17 23:30 +0100
    Re: [PATCH v2 00/26] IB: Optimize DMA mapping Jason Gunthorpe <jgunthorpe@obsidianresearch.com> - 2017-01-18 01:30 +0100

#1561064 — Re: [PATCH v2 00/26] IB: Optimize DMA mapping

On Tue, Jan 17, 2017 at 10:00:00PM +0000, Bart Van Assche wrote:
> +	/*
> +	 * qib and hfi1 use two sets of DMA operations:
> +	 * - The DMA operations of the PCIe device for SDMA.
> +	 * - dma_virt_ops for users of the qib and hfi1 drivers.
> +	 * The only purpose of @dma_device is to provide a struct device that
> +	 * provides dma_virt_ops.
> +	 */
> +	struct device dma_device;

Creating a struct device, not calling device_initialize() and then
passing it around it other places is pretty ugly and potentially
dangerous.

Is there some other way?

Can you setup ibdev to be the 'dma device' for the user side?

Jason

[toc] | [next] | [standalone]

#1561175

On Tue, Jan 17, 2017 at 10:33:16PM +0000, Bart Van Assche wrote:

> again and also the dma_device pointer from struct ib_device. Since the
> dev.dma_ops pointer in struct ib_device is not yet used dev.dma_ops can be used
> instead of the dma_device pointer.

okay great

Jason

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web