From: mkl0301@gmail.com (Lin Mac)
To: linux-arm-kernel@lists.infradead.org
Subject: DMA using data buffer vmapped in kernel space
Date: Tue, 9 Mar 2010 15:45:54 +0800 [thread overview]
Message-ID: <10d816431003082345j5438d8cdi8ad72c4fa296b684@mail.gmail.com> (raw)
In-Reply-To: <20100306193127.GA13262@n2100.arm.linux.org.uk>
2010/3/7 Russell King - ARM Linux <linux@arm.linux.org.uk>:
> On Sat, Mar 06, 2010 at 02:07:12PM +0100, Thomas Koeller wrote:
>> Am Donnerstag, 4. M?rz 2010 22:36:34 schrieb Russell King - ARM Linux:
>> > Cache maintainence is done using virtual addresses for L1, and
>> > physical addresses for L2. ?There's the need for virtual addresses
>> > to be translatable to physical addresses, which is only true for
>> > the kernel direct mapped region (pages between PAGE_OFFSET and
>> > high_memory).
>>
>> Isn't the mapping created by vmap() sufficient for the virt/phys
>> translation? In which way is this case different from a buffer
>> passed in from user space, where the constituent pages are not
>> in the directly mapped kernel region either?
>
> No different.
>
> The requirement is that dma_map_single() is passed a virtual address
> in the kernel direct-mapped memory region, which is translatable using
> virt_to_phys() and friends.
I had encounter a similiar problem and I simply allocated a new
buffer, copy the data, then DMA. It seems slow and stupid.
I'm wondering wether could I translate the vmap virt to phys(don't
know how to yet), then use phys_to_virt to get the virt in
direct-mapped memory region?
Is there other possible ways?
> Anything which requires a page table lookup to obtain the physical
> address is just not acceptable - that requires taking locks and other
> messy things, plus is grossly inefficient.
Best Regards,
Mac Lin
next prev parent reply other threads:[~2010-03-09 7:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 21:11 DMA using data buffer vmapped in kernel space Thomas Koeller
2010-03-04 21:36 ` Russell King - ARM Linux
2010-03-06 13:07 ` Thomas Koeller
2010-03-06 19:31 ` Russell King - ARM Linux
2010-03-09 7:45 ` Lin Mac [this message]
2010-03-09 9:14 ` Russell King - ARM Linux
2010-03-09 9:29 ` David Miller
2010-03-09 10:16 ` Russell King - ARM Linux
2010-03-09 10:20 ` David Miller
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=10d816431003082345j5438d8cdi8ad72c4fa296b684@mail.gmail.com \
--to=mkl0301@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).