From: Jonathan Corbet <corbet@lwn.net>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Federico Vaga <federico.vaga@gmail.com>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Pawel Osciak <pawel@osciak.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Hans Verkuil <hans.verkuil@cisco.com>,
Giancarlo Asnaghi <giancarlo.asnaghi@st.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Update VIP to videobuf2 and control framework
Date: Wed, 1 Aug 2012 07:04:18 -0600 [thread overview]
Message-ID: <20120801070418.51885637@lwn.net> (raw)
In-Reply-To: <201208010841.56941.hverkuil@xs4all.nl>
On Wed, 1 Aug 2012 08:41:56 +0200
Hans Verkuil <hverkuil@xs4all.nl> wrote:
> > The second patch adds a new memory allocator for the videobuf2. I name it
> > videobuf2-dma-streaming but I think "streaming" is not the best choice, so
> > suggestions are welcome. My inspiration for this buffer come from
> > videobuf-dma-contig (cached) version. After I made this buffer I found the
> > videobuf2-dma-nc made by Jonathan Corbet and I improve the allocator with
> > some suggestions (http://patchwork.linuxtv.org/patch/7441/). The VIP doesn't
> > work with videobu2-dma-contig and I think this solution is easier the sg.
>
> I leave this to the vb2 experts. It's not obvious to me why we would need
> a fourth memory allocator.
I first wrote my version after observing that performance dropped by a
factor of three on the OLPC XO 1.75 when using contiguous, coherent
memory. If the architecture needs to turn off caching, things really slow
down, to the point that it's unusable. There's no real reason why a V4L2
device shouldn't be able to use streaming mappings in this situation; it
performs better and doesn't eat into the limited amounts of coherent DMA
space available on some systems.
I never got my version into a mergeable state only because I finally
figured out how to bludgeon the hardware into doing s/g DMA and didn't
need it anymore. But I think it's a worthwhile functionality to have,
and, with CMA, it could be the preferred mode for a number of devices.
jon
next prev parent reply other threads:[~2012-08-01 13:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 20:17 Update VIP to videobuf2 and control framework Federico Vaga
2012-07-31 20:17 ` [PATCH 1/3] [media] adv7180: remove {query/g_/s_}ctrl Federico Vaga
2012-07-31 20:20 ` Federico Vaga
2012-08-12 1:46 ` Mauro Carvalho Chehab
2012-07-31 20:17 ` [PATCH 2/3] [media] videobuf2-dma-streaming: new videobuf2 memory allocator Federico Vaga
2012-08-20 8:03 ` Marek Szyprowski
2012-08-24 13:23 ` Federico Vaga
2012-08-24 13:40 ` Marek Szyprowski
2012-08-24 13:48 ` Federico Vaga
2012-07-31 20:17 ` [PATCH 3/3] [media] sta2x11_vip: convert to videobuf2 and control framework Federico Vaga
2012-08-06 8:17 ` [PATCH 3/3 v2] " Federico Vaga
2012-08-06 8:42 ` Hans Verkuil
2012-08-06 8:55 ` Federico Vaga
2012-07-31 20:27 ` Update VIP " Federico Vaga
2012-08-01 6:41 ` Hans Verkuil
2012-08-01 13:04 ` Jonathan Corbet [this message]
2012-08-16 11:29 ` Federico Vaga
2012-08-05 17:11 ` Federico Vaga
2012-08-06 7:26 ` Hans Verkuil
2012-08-06 7:38 ` Federico Vaga
2012-08-06 7:36 ` Hans Verkuil
2012-08-06 8:20 ` Federico Vaga
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=20120801070418.51885637@lwn.net \
--to=corbet@lwn.net \
--cc=federico.vaga@gmail.com \
--cc=giancarlo.asnaghi@st.com \
--cc=hans.verkuil@cisco.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mchehab@infradead.org \
--cc=pawel@osciak.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;
as well as URLs for NNTP newsgroup(s).