Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1227358
| From | Jerome Glisse <jglisse@redhat.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [RFC PATCH] dma/swiotlb: Add helper for device driver to opt-out from swiotlb. |
| Date | 2015-09-17 21:30 +0200 |
| Message-ID | <q9N2y-4KB-7@gated-at.bofh.it> (permalink) |
| References | <q9M6u-3l9-17@gated-at.bofh.it> <q9MJc-4n2-19@gated-at.bofh.it> <q9MJc-4n2-17@gated-at.bofh.it> <q9MSS-4yU-17@gated-at.bofh.it> <q9N2y-4KB-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Thu, Sep 17, 2015 at 03:24:25PM -0400, Konrad Rzeszutek Wilk wrote: > On Thu, Sep 17, 2015 at 03:11:14PM -0400, Jerome Glisse wrote: > > On Thu, Sep 17, 2015 at 03:06:57PM -0400, Konrad Rzeszutek Wilk wrote: > > > On Thu, Sep 17, 2015 at 03:02:51PM -0400, Konrad Rzeszutek Wilk wrote: > > > > On Thu, Sep 17, 2015 at 02:22:38PM -0400, jglisse@redhat.com wrote: > > > > > From: Jérôme Glisse <jglisse@redhat.com> > > > > > > > > > > The swiotlb dma backend is not appropriate for some devices like > > > > > GPU where bounce buffer or slow dma page allocations is just not > > > > > acceptable. With that helper device drivers can opt-out from the > > > > > swiotlb and just do sane things without wasting CPU cycles inside > > > > > the swiotlb code. > > > > > > > > What if SWIOTLB is the only one available? > > > > > > > > And what can't the devices use the TTM DMA backend which sets up > > > > buffers which don't need bounce buffer or slow dma page allocations? > > > > > > And then the followup question. If it opts out - how can it do > > > sane things without an DMA API available? It would assume physical > > > addresses match the bus addresses which is not always the sane > > > thing. > > > > This is why this is an arch specific function, on x86 with pci device, > > the driver knows what is the dma mask and thus if it can access directly > > all the memory or not. So in the end swiotlb vs no_mmu gives the same > > physical address to the device so there is no difference there. > > Not with Intel or AMD IOMMUs. The bus address it gives is not the same > as the physical address. Yes but this patch never overidde if the dma_ops are the one from any IOMMU thus it can only override if there is a 1 to 1 mapping btw bus address and physical address. Cheers, Jérôme -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[RFC PATCH] dma/swiotlb: Add helper for device driver to opt-out from swiotlb. jglisse@redhat.com - 2015-09-17 20:30 +0200
Re: [RFC PATCH] dma/swiotlb: Add helper for device driver to opt-out from swiotlb. Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> - 2015-09-17 21:10 +0200
Re: [RFC PATCH] dma/swiotlb: Add helper for device driver to opt-out from swiotlb. Jerome Glisse <jglisse@redhat.com> - 2015-09-17 21:20 +0200
Re: [RFC PATCH] dma/swiotlb: Add helper for device driver to opt-out from swiotlb. Jerome Glisse <jglisse@redhat.com> - 2015-09-17 21:30 +0200
Re: [RFC PATCH] dma/swiotlb: Add helper for device driver to opt-out from swiotlb. Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> - 2015-09-17 21:30 +0200
Re: [RFC PATCH] dma/swiotlb: Add helper for device driver to opt-out from swiotlb. Jerome Glisse <jglisse@redhat.com> - 2015-09-17 21:10 +0200
Re: [RFC PATCH] dma/swiotlb: Add helper for device driver to opt-out from swiotlb. Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> - 2015-09-17 21:40 +0200
Re: [RFC PATCH] dma/swiotlb: Add helper for device driver to opt-out from swiotlb. Jerome Glisse <jglisse@redhat.com> - 2015-09-17 21:50 +0200
Re: [RFC PATCH] dma/swiotlb: Add helper for device driver to opt-out from swiotlb. Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> - 2015-09-17 21:10 +0200
csiph-web