All of lore.kernel.org
 help / color / mirror / Atom feed
* RE: [RFC][PATCH 00/12] md raid acceleration and performance analysis
       [not found] <e9c3a7c20701222016q6e06dee6y7977f1525eacf042@mail.gmail.com>
@ 2007-02-06 23:49   ` Leech, Christopher
  0 siblings, 0 replies; 3+ messages in thread
From: Leech, Christopher @ 2007-02-06 23:49 UTC (permalink / raw)
  To: Williams, Dan J, NeilBrown, linux-raid
  Cc: Evgeniy Polyakov, Arjan van de Ven, linux-kernel

Hi Dan,

I've been looking over how your patches change the ioatdma driver.  I
like the idea of removing the multiple entry points for virtual address
vs. page struct arguments, and just using dma_addr_t for the driver
interfaces.

But, I don't think having both ioatdma and iop-adma implement map_page,
map_single, unmap_page, and unmap_single entry points is much better.
Do you see a reason why it wouldn't work to expose the generic device
for a DMA channel, and replace instances of

	dma_device->map_single(dma_chan, src, len, DMA_TO_DEVICE)

with

	dma_map_single(dma_device->dev, src, len, DMA_TO_DEVICE)

I am a little concerned about having the DMA mapping happen outside of
the driver, but the unmapping is still in the driver cleanup routine.
I'm not sure if it's really a problem, or how I'd change it though.

- Chris

^ permalink raw reply	[flat|nested] 3+ messages in thread

* RE: [RFC][PATCH 00/12] md raid acceleration and performance analysis
@ 2007-02-06 23:49   ` Leech, Christopher
  0 siblings, 0 replies; 3+ messages in thread
From: Leech, Christopher @ 2007-02-06 23:49 UTC (permalink / raw)
  To: Williams, Dan J, NeilBrown, linux-raid
  Cc: Evgeniy Polyakov, Arjan van de Ven, linux-kernel

Hi Dan,

I've been looking over how your patches change the ioatdma driver.  I
like the idea of removing the multiple entry points for virtual address
vs. page struct arguments, and just using dma_addr_t for the driver
interfaces.

But, I don't think having both ioatdma and iop-adma implement map_page,
map_single, unmap_page, and unmap_single entry points is much better.
Do you see a reason why it wouldn't work to expose the generic device
for a DMA channel, and replace instances of

	dma_device->map_single(dma_chan, src, len, DMA_TO_DEVICE)

with

	dma_map_single(dma_device->dev, src, len, DMA_TO_DEVICE)

I am a little concerned about having the DMA mapping happen outside of
the driver, but the unmapping is still in the driver cleanup routine.
I'm not sure if it's really a problem, or how I'd change it though.

- Chris

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [RFC][PATCH 00/12] md raid acceleration and performance analysis
  2007-02-06 23:49   ` Leech, Christopher
  (?)
@ 2007-02-07 22:36   ` Dan Williams
  -1 siblings, 0 replies; 3+ messages in thread
From: Dan Williams @ 2007-02-07 22:36 UTC (permalink / raw)
  To: Leech, Christopher
  Cc: NeilBrown, linux-raid, Evgeniy Polyakov, Arjan van de Ven, linux-kernel

On 2/6/07, Leech, Christopher <christopher.leech@intel.com> wrote:
> Hi Dan,
>
> I've been looking over how your patches change the ioatdma driver.  I
> like the idea of removing the multiple entry points for virtual address
> vs. page struct arguments, and just using dma_addr_t for the driver
> interfaces.
>
> But, I don't think having both ioatdma and iop-adma implement map_page,
> map_single, unmap_page, and unmap_single entry points is much better.
> Do you see a reason why it wouldn't work to expose the generic device
> for a DMA channel, and replace instances of
>
>         dma_device->map_single(dma_chan, src, len, DMA_TO_DEVICE)
>
> with
>
>         dma_map_single(dma_device->dev, src, len, DMA_TO_DEVICE)
>

I was initially concerned about a case where dma_map_single was not
equivalent to pci_map_single.  Looking now, it appears that case would
be a bug, so I will integrate this change.

> I am a little concerned about having the DMA mapping happen outside of
> the driver, but the unmapping is still in the driver cleanup routine.
> I'm not sure if it's really a problem, or how I'd change it though.
>
> - Chris

Thanks,
Dan

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2007-02-07 22:36 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <e9c3a7c20701222016q6e06dee6y7977f1525eacf042@mail.gmail.com>
2007-02-06 23:49 ` [RFC][PATCH 00/12] md raid acceleration and performance analysis Leech, Christopher
2007-02-06 23:49   ` Leech, Christopher
2007-02-07 22:36   ` Dan Williams

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.