From: PINTU KUMAR <pintu_agarwal@yahoo.com>
To: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linaro-mm-sig@lists.linaro.org" <linaro-mm-sig@lists.linaro.org>
Subject: [MM]: IOMMU and CMA buffer sharing
Date: Fri, 9 May 2014 20:22:27 -0700 (PDT) [thread overview]
Message-ID: <1399692147.36921.YahooMailNeo@web160101.mail.bf1.yahoo.com> (raw)
In-Reply-To: <1399690747.69805.YahooMailNeo@web160104.mail.bf1.yahoo.com>
Hi,
I have some queries regarding IOMMU and CMA buffer sharing.
We have an embedded linux device (kernel 3.10, RAM: 256Mb) in which camera and codec supports IOMMU but the display does not support IOMMU.
Thus for camera capture we are using iommu buffers using ION/DMABUF. But for all display rendering we are using CMA buffers.
So, the question is how to achieve buffer sharing (zero-copy) between Camera and Display using only IOMMU?
Currently we are achieving zero-copy using CMA. And we are exploring options to use IOMMU.
Now we wanted to know which option is better? To use IOMMU or CMA?
If anybody have come across these design please share your thoughts and results.
Thank You!
Regards,
Pintu
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2014-05-10 3:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-10 2:59 PINTU KUMAR
2014-05-10 3:22 ` PINTU KUMAR [this message]
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=1399692147.36921.YahooMailNeo@web160101.mail.bf1.yahoo.com \
--to=pintu_agarwal@yahoo.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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