public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthieu CASTET <matthieu.castet@parrot.com>
To: v4l2_linux <linux-media@vger.kernel.org>
Subject: videobuf cached user mapping
Date: Fri, 15 Jan 2010 16:02:10 +0100	[thread overview]
Message-ID: <4B508372.6070608@parrot.com> (raw)

Hi,

Is that possible to have user mapping cached in Memory Mapping mode ?

This means buffer allocated by mmap in userspace, will have cache
support, and it will be faster to work on it.

But how the cache coherency can be done ?

For a camera we should :
- invalidate cache before dma operation (to have not old buffer data in
the cache)
- forbid the user to access the buffer during the dma operation (to not
pollute the cache)

Is it possible ?
How can we achieve that ?

I see sync method, that seems only called after frame capture ?


Or user "User Pointers" is the solution ?
But they should have the same problems. Is there some documentation of
how "user pointer" are synchronised with dma ?

Thanks,
Matthieu



                 reply	other threads:[~2010-01-15 15:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4B508372.6070608@parrot.com \
    --to=matthieu.castet@parrot.com \
    --cc=linux-media@vger.kernel.org \
    /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