From: Robert Love <rml@tech9.net>
To: Russell Lewis <spamhole-2001-07-16@deming-os.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Looking for links: Why Linux Doesn't Page Kernel Memory?
Date: 26 Jul 2002 11:21:20 -0700 [thread overview]
Message-ID: <1027707680.2442.33.camel@sinai> (raw)
In-Reply-To: <3D418DFD.8000007@deming-os.org>
On Fri, 2002-07-26 at 10:59, Russell Lewis wrote:
> I have spent some time working on AIX, which pages its kernel memory.
> It pins the interrupt handler functions, and any data that they access,
> but does not pin the other code.
>
> I'm looking for links as to why (unless I'm mistaken) Linux doesn't do
> this, so I can better understand the system.
Better question is, why would we have page-able kernel memory?
It complicates kernel-space drastically for little gain. It is not that
we cannot, or there is a specific technical reason why not - just an
issue of taste. And lack of drugs.
Robert Love
next prev parent reply other threads:[~2002-07-26 18:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-26 17:59 Looking for links: Why Linux Doesn't Page Kernel Memory? Russell Lewis
2002-07-26 18:17 ` Andreas Dilger
2002-07-26 18:21 ` Robert Love [this message]
2002-07-26 19:10 ` Rik van Riel
2002-07-26 19:16 ` Robert Love
2002-07-26 19:18 ` Rik van Riel
2002-07-28 1:48 ` William Lee Irwin III
2002-07-28 1:56 ` Rik van Riel
2002-07-26 19:25 ` Richard B. Johnson
2002-07-26 19:33 ` Alan Cox
2002-07-26 19:43 ` Mike Castle
2002-07-27 16:24 ` David Woodhouse
2002-07-27 16:56 ` Rik van Riel
2002-07-28 0:59 ` Daniel Phillips
2002-07-28 20:07 ` Alan Cox
2002-07-28 0:40 ` Daniel Phillips
2002-07-28 0:57 ` William Lee Irwin III
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=1027707680.2442.33.camel@sinai \
--to=rml@tech9.net \
--cc=linux-kernel@vger.kernel.org \
--cc=spamhole-2001-07-16@deming-os.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.