public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Michal Nazarewicz <mina86@mina86.com>,
	Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
	Hans Verkuil <hansverk@cisco.com>, Qing Xu <qingx@marvell.com>,
	Linux Media Mailing List <linux-media@vger.kernel.org>,
	Neil Johnson <realdealneil@gmail.com>,
	Robert Jarzmik <robert.jarzmik@free.fr>,
	Uwe Taeubert <u.taeubert@road.de>,
	"Karicheri, Muralidharan" <m-karicheri2@ti.com>,
	Eino-Ville Talvala <talvala@stanford.edu>
Subject: Re: [RFD] frame-size switching: preview / single-shot use-case
Date: Fri, 18 Feb 2011 10:33:12 -0200	[thread overview]
Message-ID: <4D5E6708.9000500@infradead.org> (raw)
In-Reply-To: <201102181131.30920.laurent.pinchart@ideasonboard.com>

Em 18-02-2011 08:31, Laurent Pinchart escreveu:
> It's a trade-off between memory and speed. Preallocating still image capture 
> buffers will give you better snapshot performances, at the expense of memory.
> 
> The basic problems we have here is that taking snapshots is slow with the 
> current API if we need to stop capture, free buffers, change the format, 
> allocate new buffers (and perform cache management operations) and restart the 
> stream. To fix this we're considering a way to preallocate still image capture 
> buffers, but I'm open to proposals for other ways to solve the issue :-)

>From the above operations, considering that CMA is used to reserve a
non-shared memory with enough space for the new buffer size/qtd, I don't
think that the most expensive operation would be to realloc the memory.

The logic to stop/start streaming seems to be the most consuming one, as driver
will need to wait for the current I/O operation to complete, and this can
take hundreds of milisseconds (the duration of one frame).

How much time would CMA need to free and re-allocate the buffers for, let's
say, something in the range of 1-10 MB, on a pre-allocated, non shared memory
space?

Cheers
Mauro

  parent reply	other threads:[~2011-02-18 12:33 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4D5D9B57.3090809@gmail.com>
2011-02-17 23:09 ` [RFD] frame-size switching: preview / single-shot use-case Michal Nazarewicz
2011-02-18 10:31   ` Laurent Pinchart
2011-02-18 11:37     ` Michal Nazarewicz
2011-02-18 12:57       ` Laurent Pinchart
2011-02-18 13:19         ` Michal Nazarewicz
2011-02-18 13:21           ` Laurent Pinchart
2011-02-18 14:05             ` Michal Nazarewicz
2011-02-18 14:13               ` Laurent Pinchart
2011-02-18 12:33     ` Mauro Carvalho Chehab [this message]
2011-02-18 12:36       ` Laurent Pinchart
2011-02-18 12:46       ` Michal Nazarewicz
2011-02-15 17:33 Guennadi Liakhovetski
2011-02-15 17:41 ` Karicheri, Muralidharan
2011-02-16  2:50 ` Qing Xu
2011-02-16  7:42   ` Guennadi Liakhovetski
2011-02-16  8:49     ` Hans Verkuil
2011-02-16  9:02       ` Guennadi Liakhovetski
2011-02-16  9:11         ` Laurent Pinchart
2011-02-16 10:35           ` Guennadi Liakhovetski
2011-02-17 16:46             ` Guennadi Liakhovetski
2011-02-18  9:47               ` Laurent Pinchart
2011-02-17 19:04             ` Mauro Carvalho Chehab
2011-02-17 19:26               ` Guennadi Liakhovetski
2011-02-17 20:46                 ` Mauro Carvalho Chehab
2011-02-17 21:13                   ` Guennadi Liakhovetski
2011-02-18 10:27               ` Laurent Pinchart
2011-02-16  2:55 ` Qing Xu
2011-02-17 18:27 ` Mauro Carvalho Chehab

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=4D5E6708.9000500@infradead.org \
    --to=mchehab@infradead.org \
    --cc=g.liakhovetski@gmx.de \
    --cc=hansverk@cisco.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=m-karicheri2@ti.com \
    --cc=mina86@mina86.com \
    --cc=qingx@marvell.com \
    --cc=realdealneil@gmail.com \
    --cc=robert.jarzmik@free.fr \
    --cc=talvala@stanford.edu \
    --cc=u.taeubert@road.de \
    /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