From: Dave Airlie <airlied@gmail.com>
To: Sumit Semwal <sumit.semwal@ti.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-mm@kvack.org,
linaro-mm-sig@lists.linaro.org, dri-devel@lists.freedesktop.org,
linux-media@vger.kernel.org, linux@arm.linux.org.uk,
arnd@arndb.de, jesse.barker@linaro.org, daniel@ffwll.ch
Subject: Re: [Linaro-mm-sig] [RFC 1/2] dma-buf: Introduce dma buffer sharing mechanism
Date: Wed, 12 Oct 2011 13:41:57 +0100 [thread overview]
Message-ID: <CAPM=9tzHOa5Dbe=SQz+AURMMbio4L7qoS8kUT3Ek0+HdtkrH4g@mail.gmail.com> (raw)
In-Reply-To: <1318325033-32688-2-git-send-email-sumit.semwal@ti.com>
On Tue, Oct 11, 2011 at 10:23 AM, Sumit Semwal <sumit.semwal@ti.com> 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:
> - a new buffer-object to be created with fixed size.
> - different devices to 'attach' themselves to this buffer, to facilitate
> backing storage negotiation, using dma_buf_attach() API.
> - association of a file pointer with each user-buffer and associated
> allocator-defined operations on that buffer. This operation is called the
> 'export' operation.
> - this exported buffer-object to be shared with the other entity by asking for
> its 'file-descriptor (fd)', and sharing the fd across.
> - a received fd to get the buffer object back, where it can be accessed using
> the associated exporter-defined operations.
> - the exporter and user to share the scatterlist using get_scatterlist and
> put_scatterlist operations.
>
> Atleast one 'attach()' call is required to be made prior to calling the
> get_scatterlist() operation.
>
> Couple of building blocks in get_scatterlist() are added to ease introduction
> of sync'ing across exporter and users, and late allocation by the exporter.
>
> mmap() file operation is provided for the associated 'fd', as wrapper over the
> optional allocator defined mmap(), to be used by devices that might need one.
Why is this needed? it really doesn't make sense to be mmaping objects
independent of some front-end like drm or v4l.
how will you know what contents are in them, how will you synchronise
access. Unless someone has a hard use-case for this I'd say we drop it
until someone does.
Dave.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-10-12 12:41 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 9:23 [RFC 0/2] " Sumit Semwal
2011-10-11 9:23 ` [RFC 1/2] dma-buf: " Sumit Semwal
2011-10-12 12:41 ` Dave Airlie [this message]
2011-10-12 13:28 ` [Linaro-mm-sig] " Rob Clark
2011-10-12 13:35 ` Dave Airlie
2011-10-12 13:50 ` Rob Clark
2011-10-12 14:01 ` Dave Airlie
2011-10-12 14:24 ` Rob Clark
2011-10-12 14:34 ` Dave Airlie
2011-10-12 14:49 ` Daniel Vetter
2011-10-12 15:15 ` Rob Clark
2011-10-14 10:00 ` Tomasz Stanislawski
2011-10-14 14:13 ` Sumit Semwal
2011-10-14 15:34 ` Rob Clark
2011-10-14 15:35 ` Daniel Vetter
2011-11-03 8:04 ` Marek Szyprowski
2011-11-08 16:59 ` Clark, Rob
2011-11-08 17:42 ` [RFC 1/2] dma-buf: Introduce dma buffer sharing mechanismch Daniel Vetter
2011-11-08 17:55 ` Russell King - ARM Linux
2011-11-08 18:43 ` Daniel Vetter
2011-11-28 7:47 ` Marek Szyprowski
2011-11-28 10:34 ` Daniel Vetter
2011-11-25 14:13 ` [Linaro-mm-sig] [RFC 1/2] dma-buf: Introduce dma buffer sharing mechanism Dave Airlie
2011-11-25 16:02 ` Daniel Vetter
2011-11-25 16:15 ` Dave Airlie
2011-11-25 16:28 ` Dave Airlie
2011-11-26 14:00 ` Daniel Vetter
2011-11-27 6:59 ` Rob Clark
2011-12-01 5:51 ` Semwal, Sumit
2011-12-01 5:55 ` Semwal, Sumit
2011-10-11 9:23 ` [RFC 2/2] dma-buf: Documentation for buffer sharing framework Sumit Semwal
2011-10-12 22:30 ` Randy Dunlap
2011-10-13 4:48 ` Semwal, Sumit
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPM=9tzHOa5Dbe=SQz+AURMMbio4L7qoS8kUT3Ek0+HdtkrH4g@mail.gmail.com' \
--to=airlied@gmail.com \
--cc=arnd@arndb.de \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jesse.barker@linaro.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@arm.linux.org.uk \
--cc=sumit.semwal@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox