From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Steven Toth <stoth@kernellabs.com>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
Kazunori Kobayashi <kkobayas@igel.co.jp>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Damian Hobson-Garcia <dhobsong@igel.co.jp>,
Hans Verkuil <hans.verkuil@cisco.com>,
Marek Szyprowski <m.szyprowski@samsung.com>
Subject: Re: Memory freeing when dmabuf fds are exported with VIDIOC_EXPBUF
Date: Mon, 01 Aug 2016 19:56:33 +0300 [thread overview]
Message-ID: <1625689.yhf3QdObg4@avalon> (raw)
In-Reply-To: <CALzAhNX-AhiaVJ3UrTodHRZg__h5itwCqwJw9FhhJoT_K4sp5w@mail.gmail.com>
On Monday 01 Aug 2016 12:16:25 Steven Toth wrote:
> > That's a good question. On one extreme an application trying to allocate
> > 32 50MB buffers would seem suspicious to me, but on the other hand it
> > would be difficult to answer the question in a way that can be translated
> > into code.
>
> 8k video in the ARGB 8bit 4:4:4 colorspace, would need a 126MB per frame
> buffer.
Hopefully not 32 of them though.
There's no easy way to compute an accurate limit, but maybe we could do
improve the current situation with some heuristics based on the maximum
resolution a device can capture.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2016-08-01 17:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 7:51 Memory freeing when dmabuf fds are exported with VIDIOC_EXPBUF Kazunori Kobayashi
2016-07-27 12:57 ` Laurent Pinchart
2016-08-01 10:56 ` Hans Verkuil
2016-08-01 12:17 ` Laurent Pinchart
2016-08-01 12:27 ` Hans Verkuil
2016-08-01 13:49 ` Laurent Pinchart
2016-08-01 13:59 ` Hans Verkuil
2016-08-01 16:02 ` Laurent Pinchart
2016-08-01 16:16 ` Steven Toth
2016-08-01 16:56 ` Laurent Pinchart [this message]
2016-08-03 3:23 ` Damian Hobson-Garcia
2017-10-03 15:00 ` Nicolas Dufresne
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=1625689.yhf3QdObg4@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=dhobsong@igel.co.jp \
--cc=hans.verkuil@cisco.com \
--cc=hverkuil@xs4all.nl \
--cc=kkobayas@igel.co.jp \
--cc=linux-media@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=stoth@kernellabs.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