From: Orjan Friberg <of@flatfrog.com>
To: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: copy_to_user speed from dma_alloc_coherent vs. kmalloc buffer
Date: Wed, 20 Apr 2011 19:09:29 +0200 [thread overview]
Message-ID: <4DAF1349.6020008@flatfrog.com> (raw)
In-Reply-To: <4DAEF7F0.4080207@flatfrog.com>
On 2011-04-20 17:12, Orjan Friberg wrote:
> What are my options (besides using mmap)?
It looks like kmalloc + dma_map_single for the DMA destination buffer
and then dma_sync_single_for_{cpu,device} around the call to
copy_to_user pretty much does the trick. At least the %sys load
measured with mpstat goes from 13% to 2%.
--
Orjan Friberg
FlatFrog Laboratories AB
prev parent reply other threads:[~2011-04-20 17:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 15:12 copy_to_user speed from dma_alloc_coherent vs. kmalloc buffer Orjan Friberg
2011-04-20 17:09 ` Orjan Friberg [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=4DAF1349.6020008@flatfrog.com \
--to=of@flatfrog.com \
--cc=linux-omap@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