public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Marek Szyprowski <m.szyprowski@samsung.com>
To: KyongHo Cho <pullip.cho@samsung.com>
Cc: linaro-mm-sig@lists.linaro.org, linux-media@vger.kernel.org,
	Tomasz Stanislawski <t.stanislaws@samsung.com>,
	Kyungmin Park <kyungmin.park@samsung.com>
Subject: Re: [Linaro-mm-sig] Buffer sharing proof-of-concept
Date: Tue, 02 Aug 2011 16:48:48 +0200	[thread overview]
Message-ID: <4E380E50.8030302@samsung.com> (raw)
In-Reply-To: <CAHQjnONh3=dRfL-_6gBT2pa=erRKUe9OMiMQjXDQyN493Gz4tw@mail.gmail.com>

Hello,

On 2011-08-02 13:59, KyongHo Cho wrote:
> On Tue, Aug 2, 2011 at 6:48 PM, Marek Szyprowski
> <m.szyprowski@samsung.com>  wrote:
>> Hello Everyone,
>>
>> This patchset introduces the proof-of-concept infrastructure for buffer
>> sharing between multiple devices using file descriptors. The infrastructure
>> has been integrated with V4L2 framework, more specifically videobuf2 and two
>> S5P drivers FIMC (capture interface) and TV drivers, but it can be easily
>> used by other kernel subsystems, like DRI.
>>
>> In this patch the buffer object has been simplified to absolute minimum - it
>> contains only the buffer physical address (only physically contiguous
>> buffers are supported), but this can be easily extended to complete scatter
>> list in the future.
>>
>
> Is this patch set an attempt to share a buffer between different
> processes via open file descriptors?
> Your patches seems to include several constructs to pack information
> about a buffer in an open file descriptor
> and to unpack it.
>
> I don't have any idea what is the purpose of your attempts.
> Is it the first step to the unified memory model that is being
> discussed in Linaro?

Yes, these patches were posted to demonstrate how sharing the buffers 
between different devices (currently only v4l2 based) can be 
implemented. We are discussing the idea of sharing the buffers on Memory 
Management summit on Linaro Sprint in Cambourne.

Best regards
-- 
Marek Szyprowski
Samsung Poland R&D Center



  reply	other threads:[~2011-08-02 14:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-02  9:48 Buffer sharing proof-of-concept Marek Szyprowski
2011-08-02  9:49 ` [PATCH 1/6] drivers: base: add shared buffer framework Marek Szyprowski
2011-08-02 18:09   ` [Linaro-mm-sig] " Clark, Rob
2011-08-02  9:50 ` [PATCH 2/6] v4l: add buffer exporting via shrbuf Marek Szyprowski
2011-08-02  9:52 ` [PATCH 3/6] v4l: vb2: add support for shared buffer (shrbuf) Marek Szyprowski
2011-08-02  9:53 ` [PATCH 4/6] v4l: vb2: integrate dma-contig allocator with shrbuf Marek Szyprowski
2011-08-02  9:53 ` [PATCH 5/6] v4l: fimc: integrate capture i-face " Marek Szyprowski
2011-08-02  9:54 ` [PATCH 6/6] v4l: s5p-tv: mixer: integrate " Marek Szyprowski
2011-08-02 11:59 ` [Linaro-mm-sig] Buffer sharing proof-of-concept KyongHo Cho
2011-08-02 14:48   ` Marek Szyprowski [this message]
2011-08-02 15:44 ` Jordan Crouse
2011-08-03  9:33   ` Tom Cooksey
2011-08-03 15:12     ` Jordan Crouse
2011-08-04  8:58       ` Daniel Vetter
2011-08-04 11:14         ` Clark, Rob
2011-08-04 12:34           ` Daniel Vetter
2011-08-04 16:19             ` Clark, Rob

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=4E380E50.8030302@samsung.com \
    --to=m.szyprowski@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linaro-mm-sig@lists.linaro.org \
    --cc=linux-media@vger.kernel.org \
    --cc=pullip.cho@samsung.com \
    --cc=t.stanislaws@samsung.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