LKML Archive on
help / color / mirror / Atom feed
From: Sri Ram Vemulpali <>
To: Ankita Garg <>
Cc: Kernel-newbies <>,
	linux-kernel-mail <>
Subject: Re: Mapping memory between kernel and user space
Date: Tue, 15 Feb 2011 12:15:08 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

As was suggested I started reading chap 15v from LDD. I ran more into
confusion state.

I know that virtual address(process space), linear address
(segmentation) and physical address. And how are they resolved from
virtual to physical.
But coming to kernel they distinguish logical address from virtual
address. What is the main difference.
Also, they emphasize on high memory and low memory. Why can not high
memory can be mapped in to kernel completely.
Why is that kernel has less visibility of complete space available on RAM.
Linux MM is it a very specific implementation of linux, or Is that a
traditional implementation.

what is very minimal implementation of MMU for real time systems.

Thanks in advance.


On Tue, Feb 15, 2011 at 12:54 AM, Ankita Garg <> wrote:
> On Wed, Feb 09, 2011 at 06:45:42PM -0500, Sri Ram Vemulpali wrote:
>> Hi all,
>>   How do I map some space between kernel and user space. Can anyone
>> point me in to right direction. I was trying to map the packets from
>> my netfilter function to kernel user space, to avoid over head of
>> copying. Thanks in advance.
> You can take a look at remap_pfn_range() routine when implementing mmap
> in your driver.
> --
> Regards,
> Ankita Garg (
> Linux Technology Center
> IBM India Systems & Technology Labs,
> Bangalore, India


  reply	other threads:[~2011-02-15 17:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-09 23:45 Sri Ram Vemulpali
2011-02-15  5:54 ` Ankita Garg
2011-02-15 17:15   ` Sri Ram Vemulpali [this message]
2011-02-16  5:09     ` Ankita Garg
2011-02-16  5:52     ` Rajat Sharma
     [not found]       ` <>
2011-02-16 15:32         ` Rajat Sharma

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \ \
    --subject='Re: Mapping memory between kernel and user space' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).