kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: mulyadi.santosa@gmail.com (Mulyadi Santosa)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Basic HighMeM Question
Date: Wed, 29 Jun 2011 16:03:05 +0700	[thread overview]
Message-ID: <BANLkTimzYTQJjcPmqQR4QP4jFyZu_m2u0A@mail.gmail.com> (raw)
In-Reply-To: <BANLkTinEd2rOvzvA4wRQaeDsOnOD=9--Dw@mail.gmail.com>

Hi :)

On Wed, Jun 29, 2011 at 14:34, Paraneetharan Chandrasekaran
<paraneetharanc@gmail.com> wrote:
> Thanks Mulyadi for your clarifications!
> I am not getting the idea of "borrowing" last run process's address space. A
> kernel thread refers only the addresses in kernel's address space (low-mem
> area) which is mapped already, isnt it? How does the address space of last
> run task comes into picture?

Think like this: kernel thread is supposed to be operate entirely in
kernel space, right?

Then, you also agree that kernel address space is the same for all
running processess, correct? The only thing differs is their user
space mapping, right?

Based on this facts, kernel threads could simply use any last
scheduled process address space descriptor. Remember: its descriptor
(thus logically use its mapping too). Is it fine? sure... check the
above facts if you are confused. By using this trick, we save few
kilobytes by not allocating memory for yet another virtual memory
space descriptor (mm_struct and its VMAs)

-- 
regards,

Mulyadi Santosa
Freelance Linux trainer and consultant

blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com

      reply	other threads:[~2011-06-29  9:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-27  9:12 Basic HighMeM Question piyush moghe
2011-06-27  9:28 ` Prabhu nath
     [not found]   ` <BANLkTinp6_n0z6OAzo1R6sq_nLynyo_3Xg@mail.gmail.com>
2011-06-27 11:15     ` Prabhu nath
2011-06-28  5:51       ` piyush moghe
2011-06-28 10:16         ` Mulyadi Santosa
2011-06-28 10:49           ` Prabhu nath
2011-06-28 15:26             ` Mulyadi Santosa
2011-06-29  6:30               ` piyush moghe
2011-06-29  6:38                 ` Mulyadi Santosa
2011-06-29  7:34                   ` Paraneetharan Chandrasekaran
2011-06-29  9:03                     ` Mulyadi Santosa [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=BANLkTimzYTQJjcPmqQR4QP4jFyZu_m2u0A@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).