On Tue, Apr 18, 2017 at 09:42:20AM -0600, Logan Gunthorpe wrote:
>
>
> On 18/04/17 08:27 AM, Konrad Rzeszutek Wilk wrote:
> > Interesting that you didn't CC any of the maintainers. Could you
> > do that in the future please?
>
> Please read the cover le
On Tue, Apr 18, 2017 at 02:13:59PM +, David Laight wrote:
> From: Logan Gunthorpe
> > Sent: 13 April 2017 23:05
> > Straightforward conversion to the new helper, except due to
> > the lack of error path, we have to warn if unmapable memory
> > is ever present in the sgl.
Interesting that you
+EXPORT_SYMBOL(is_dmabuf_sync_supported);
_GPL ?
I would also prefix it with 'dmabuf_is_sync_supported' just to make
all of the libraries call start with 'dmabuf'
Seems better. Will change it to dmabuf_is_sync_supported, and use
EXPORT_SYMBOL_GPL.
One thing thought - while I
On Tue, Aug 13, 2013 at 06:19:35PM +0900, Inki Dae wrote:
This patch adds a buffer synchronization framework based on DMA BUF[1]
and and based on ww-mutexes[2] for lock mechanism.
The purpose of this framework is to provide not only buffer access control
to CPU and DMA but also easy-to-use
On Fri, Dec 23, 2011 at 03:22:35PM +0530, Semwal, Sumit wrote:
Hi Konrad,
On Tue, Dec 20, 2011 at 10:06 PM, Konrad Rzeszutek Wilk
konrad.w...@oracle.com wrote:
On Mon, Dec 19, 2011 at 02:03:30PM +0530, Sumit Semwal wrote:
This is the first step in defining a dma buffer sharing mechanism
On Mon, Dec 19, 2011 at 02:03:30PM +0530, Sumit Semwal wrote:
This is the first step in defining a dma buffer sharing mechanism.
A new buffer object dma_buf is added, with operations and API to allow easy
sharing of this buffer object across devices.
The framework allows:
- different
On Fri, Dec 02, 2011 at 02:27:31PM +0530, Sumit Semwal wrote:
This is the first step in defining a dma buffer sharing mechanism.
A new buffer object dma_buf is added, with operations and API to allow easy
sharing of this buffer object across devices.
The framework allows:
- different
conditions did you expose this fault?
You also might want to mention that needn't be a physical address as
a hardware IOMMU can (and most likely) will return a bus address where
physical != bus address.
Otherwise you can stick 'Reviewed-by: Konrad Rzeszutek Wilk
konrad.w...@oracle.com'
on it.
remapping
.. snip..
But 64KB or 1MB physically contiguous memory is better than 4KB page in the
point of performance.
Could you explain that in more details please? I presume you are
talking about a CPU that has a MMU unit, right?
--
To unsubscribe from this list: send the line unsubscribe linux-media
On Mon, Dec 06, 2010 at 02:30:52PM +0100, Jiri Slaby wrote:
mem-dma_handle is a dma address obtained by dma_alloc_coherent which
needn't be a physical address in presence of IOMMU. So ensure we are
Could you use PFN_DOWN(virt_to_phys(mem-vaddr)?
remapping (remap_pfn_range) the right page in
+* The Virtual Contiguous Memory Manager
+
+The VCMM was built to solve the system-wide memory mapping issues that
+occur when many bus-masters have IOMMUs.
+
+An IOMMU maps device addresses to physical addresses. It also
+insulates the system from spurious or malicious device bus
On Fri, Aug 20, 2010 at 11:50:42AM +0200, Michal Nazarewicz wrote:
The Contiguous Memory Allocator framework is a set of APIs for
allocating physically contiguous chunks of memory.
Various chips require contiguous blocks of memory to operate. Those
chips include devices such as cameras,
On Fri, Aug 20, 2010 at 11:50:43AM +0200, Michal Nazarewicz wrote:
The SysFS development interface lets one change the map attribute
at run time as well as observe what regions have been reserved.
Signed-off-by: Michal Nazarewicz m.nazarew...@samsung.com
Signed-off-by: Kyungmin Park
On Wed, Aug 18, 2010 at 12:01:35PM +0900, Kyungmin Park wrote:
Are there any comments or ack?
Is there a git tree and/or link to the latest version that is based on
top 2.6.36-rc1?? I somehow seem to have lost the v3 of these patches.
--
To unsubscribe from this list: send the line unsubscribe
14 matches
Mail list logo
