From: Ravi Gupta <dceravigupta@gmail.com>
To: David Howells <dhowells@redhat.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: Memory Mapping a char array in User Space
Date: Tue, 27 Jul 2010 12:34:04 +0530 [thread overview]
Message-ID: <AANLkTimLDLO5xr+sUPTB6GZph+T_-kf-ZHLox2b=PMHO@mail.gmail.com> (raw)
In-Reply-To: <918.1280173321@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 488 bytes --]
Hi David,
Thanks for the quick reply. One more thing, in the end I have to memory map
a DMA buffer allocated using pci_alloc_consisten() function to user space.
*> I think you should be leaving the mapping to the core VM routines.*
*> Furthermore, I don't think *you* should be calling remap_pfn_range().*
Let say I have allocated a page using __get_free_pages(). But how would the
core VM routines knows that which page I want to memory map? If possible,
please explain with example.
[-- Attachment #2: Type: text/html, Size: 573 bytes --]
prev parent reply other threads:[~2010-07-27 7:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 17:28 Memory Mapping a char array in User Space Ravi Gupta
2010-07-26 19:42 ` David Howells
2010-07-27 7:04 ` Ravi Gupta [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='AANLkTimLDLO5xr+sUPTB6GZph+T_-kf-ZHLox2b=PMHO@mail.gmail.com' \
--to=dceravigupta@gmail.com \
--cc=dhowells@redhat.com \
--cc=linuxppc-dev@lists.ozlabs.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).