[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAF6AEGtGR0-vtfrP4i++kBxb2wGgGzv2MDu-K3CjmhEBXQyDnA@mail.gmail.com>
Date: Fri, 23 Dec 2011 11:10:07 -0600
From: Rob Clark <robdclark@...il.com>
To: "Semwal, Sumit" <sumit.semwal@...com>
Cc: Arnd Bergmann <arnd@...db.de>, Daniel Vetter <daniel@...ll.ch>,
Alan Cox <alan@...rguk.ukuu.org.uk>, linux@....linux.org.uk,
linux-kernel@...r.kernel.org, dri-devel@...ts.freedesktop.org,
linaro-mm-sig@...ts.linaro.org, linux-mm@...ck.org,
linux-media@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [Linaro-mm-sig] [RFC v2 1/2] dma-buf: Introduce dma buffer
sharing mechanism
On Fri, Dec 23, 2011 at 4:00 AM, Semwal, Sumit <sumit.semwal@...com> wrote:
> On Wed, Dec 21, 2011 at 10:57 PM, Arnd Bergmann <arnd@...db.de> wrote:
>> On Tuesday 20 December 2011, Daniel Vetter wrote:
>>> > I'm thinking for a first version, we can get enough mileage out of it by saying:
>>> > 1) only exporter can mmap to userspace
>>> > 2) only importers that do not need CPU access to buffer..
>
> Thanks Rob - and the exporter can do the mmap outside of dma-buf
> usage, right?
Yes
> I mean, we don't need to provide an mmap to dma_buf()
> and restrict it to exporter, when the exporter has more 'control' of
> the buffer anyways.
No, if it is only for the exporter, it really doesn't need to be in
dmabuf (ie. the exporter already knows how he is)
BR,
-R
>>
> BR,
> ~Sumit.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists