From: mulyadi.santosa@gmail.com (Mulyadi Santosa)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Clarification on memory mapping
Date: Wed, 1 Jun 2011 23:00:01 +0700 [thread overview]
Message-ID: <BANLkTinn30HPxDVDUUR3+31U-16wuDNuiA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTin0Ge_b7S8kedbMx4NVcwQdm92etQ@mail.gmail.com>
On Wed, Jun 1, 2011 at 13:34, sandeep kumar <coolsandyforyou@gmail.com> wrote:
> Hi,
> I am new to kernel programming. Last few days i have been?reading about
> memory management, memory mapping etc.,
> But i?could not?put the things together.
> Here i need clarifications regarding the few things whether wat i understood
> is right or not.
>
> 1) Mapping means bringing a device memory which is not in the address space
> of kernel/user to its address space.
>
> ioremap() :
> 2) ioremap?does mapping of a particular i/o device to kernel logical memory
> address.
>
> mmap()
> 3) mmap does the mapping of a device memory to user space virtual address.
it maps either a file or you do anonymous page allocation here. I
doubt it deals with device....at least directly....
> kmap()
> 4)?gets a kernel virtual address of an allocated high memory page.
>
> 5) And finally memory mapping does a manipulation of a PTE.
>
> Tell if i have interpreted anything wrong and please correct me.
>
> Thank you
>
>
>
> --
> With regards,
> Sandeep Kumar Anantapalli,
>
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
>
--
regards,
Mulyadi Santosa
Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
next prev parent reply other threads:[~2011-06-01 16:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 6:34 Clarification on memory mapping sandeep kumar
2011-06-01 16:00 ` Mulyadi Santosa [this message]
2011-06-01 17:38 ` Prashant Shah
2011-06-01 23:47 ` Dave Hylands
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=BANLkTinn30HPxDVDUUR3+31U-16wuDNuiA@mail.gmail.com \
--to=mulyadi.santosa@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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).