From: paraneetharanc@gmail.com (Paraneetharan Chandrasekaran)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Basic HighMeM Question
Date: Wed, 29 Jun 2011 13:04:34 +0530 [thread overview]
Message-ID: <BANLkTinEd2rOvzvA4wRQaeDsOnOD=9--Dw@mail.gmail.com> (raw)
In-Reply-To: <BANLkTimuh4NDb_HhzuSCAKejCGVbRmuGvQ@mail.gmail.com>
On 29 June 2011 12:08, Mulyadi Santosa <mulyadi.santosa@gmail.com> wrote:
> Hi :)
>
> On Wed, Jun 29, 2011 at 13:30, piyush moghe <pmkernel@gmail.com> wrote:
> > Thanks Mulyadi and Prabhu for your enlightening description.
>
> You welcome :)
>
> > What a plight!!! memory has become soo cheap nowadays that I don't have
> less
> > than 1GB system and difficult to find someone in my knowledge having less
> > than 1 GB memory.
>
> In embedded world, it's still common scenario.... so it depends on
> which side we see it :) That's the flexibility Linux kernel tries to
> show...it does well on big memory machine...but it can also run in
> small amount of memory... of course, with the right user space
> applications :) (hint: Linux slitaz, puppy, tiny core...)
>
>
> > Although does this means that pages in FCOM will never have page fault?
>
> Everything mapped in kernel space ( I stress the word "mapped") is
> designed to stay all the time in RAM in Linux kernel context. So based
> on that AFAIK, we won't get page fault in kernel space. This is
> strictly design choice IMHO.
>
> >and
> > if this is true is this the reason why we assign NULL to memory
> descriptor (
> > mm_struct ) for kernel threads?
>
> because kernel threads don't need to have specific address space owned
> to them. They can simply "borrow" last scheduled process' address
> space. After all, they just operate in kernel space, which is the same
> for all processes, be it kernel threads or normal task.
>
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?
>
> --
> regards,
>
> Mulyadi Santosa
> Freelance Linux trainer and consultant
>
> blog: the-hydra.blogspot.com
> training: mulyaditraining.blogspot.com
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
--
Regards,
Paraneetharan C
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110629/c7e9477e/attachment.html
next prev parent reply other threads:[~2011-06-29 7:34 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 [this message]
2011-06-29 9:03 ` Mulyadi Santosa
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='BANLkTinEd2rOvzvA4wRQaeDsOnOD=9--Dw@mail.gmail.com' \
--to=paraneetharanc@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).