From: michi1@michaelblizek.twilightparadox.com (michi1 at michaelblizek.twilightparadox.com)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Kernel Memory
Date: Thu, 21 Jun 2012 17:48:25 +0200 [thread overview]
Message-ID: <20120621154824.GA2280@grml> (raw)
In-Reply-To: <CAJ61zBA++CFmTHSb2cRr=cKJdTkVYsSVs3_igESbbf21gWaqCQ@mail.gmail.com>
Hi!
On 17:57 Thu 21 Jun , Vijay Chauhan wrote:
> Hello,
>
> I am newbie.
> It has been said "kernel memory is not pageable"
> What does it mean? There is no concept of kernel virtual address?
>
> Any simple explanation will help me to udnerstand.
The right term is actually "kernel memory is not swappable". Swapping means
writing inactive memory to disk and then using it for something else. Kernel
memory not being swappable is a design decicion made in the early linux days.
Operating systems which swap kernel memory need to isolate everything which
should not be swappd out (e.g. things needed for swap-in, realtime stuff,
security sensitive data, ...). This is quite a bit of work. I also guess it is
pretty pointless nowadays. Installed memory and is getting so huge that virtual
memory developers have a hard time trying to keep cpu-usage overhead for
swapping user space memory low.
> There is no concept of kernel virtual address?
Kernel memory uses virtual addresses as well. However, these the entire system
memory is continuously mapped somewhere in the virtual address space. The
drawback is that fragmentation turns allocation of large continuous memory
regions into a game of luck.
There is also an virtual address area (vmalloc) which is used to dynamically
map multiple scattered pages to a continuous region. But this is rather slow
and rarely used.
You might want to take a look at: http://lwn.net/Kernel/LDD3/
-Michi
--
programing a layer 3+4 network protocol for mesh networks
see http://michaelblizek.twilightparadox.com
next prev parent reply other threads:[~2012-06-21 15:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-21 12:27 Kernel Memory Vijay Chauhan
2012-06-21 13:35 ` HowKernel StuffWorks
2012-06-21 13:40 ` kishore sheik ahamed
2012-06-22 18:23 ` Vijay Chauhan
2012-06-21 13:44 ` Arun KS
2012-06-21 14:02 ` AFT
2012-06-21 15:48 ` michi1 at michaelblizek.twilightparadox.com [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-05-17 7:11 Kernel memory Ronit Halder
2016-05-17 15:05 ` Valdis.Kletnieks at vt.edu
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=20120621154824.GA2280@grml \
--to=michi1@michaelblizek.twilightparadox.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).