From: sidc7 <siddhartha.chhabra@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Kernel vs user memory
Date: Fri, 16 Jan 2009 18:56:52 -0800 (PST) [thread overview]
Message-ID: <21512362.post@talk.nabble.com> (raw)
The kernel maintains a free list of pages that are free in physical memory. I
was wondering, are these pages in the kernel space ? They are not mapped to
any of the user address space for sure, so will they be in the kernel memory
?
Thanks
--
View this message in context: http://www.nabble.com/Kernel-vs-user-memory-tp21512362p21512362.html
Sent from the linux-kernel mailing list archive at Nabble.com.
next reply other threads:[~2009-01-17 2:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-17 2:56 sidc7 [this message]
2009-01-17 4:16 ` Kernel vs user memory Bryan Donlan
2009-01-17 4:21 ` sidc7
2009-01-17 5:26 ` Bryan Donlan
[not found] ` <49f90a801003181710v5e08ccc8jdd26ec899e75bdb9@mail.gmail.com>
2010-03-19 0:28 ` Bryan Donlan
[not found] ` <49f90a801003181747m5078d9c2y3cc8421203a7b1e6@mail.gmail.com>
2010-03-19 1:06 ` Bryan Donlan
2010-03-19 1:29 ` Siddhartha Chhabra
2009-01-17 6:26 ` H. Peter Anvin
2009-01-17 6:34 ` sidc7
2009-01-17 6:38 ` H. Peter Anvin
2009-01-17 6:42 ` sidc7
2009-01-17 7:27 ` H. Peter Anvin
2009-01-19 20:03 ` sidc7
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=21512362.post@talk.nabble.com \
--to=siddhartha.chhabra@gmail.com \
--cc=linux-kernel@vger.kernel.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