From: David Woodhouse <dwmw2@infradead.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Russell Lewis <spamhole-2001-07-16@deming-os.org>,
linux-kernel@vger.kernel.org
Subject: Re: Looking for links: Why Linux Doesn't Page Kernel Memory?
Date: Sat, 27 Jul 2002 17:24:58 +0100 [thread overview]
Message-ID: <16918.1027787098@redhat.com> (raw)
In-Reply-To: <1027712005.14773.12.camel@irongate.swansea.linux.org.uk>
alan@lxorguk.ukuu.org.uk said:
> Memory is relatively cheap, and the complexity of such a paging
> kernel is huge (you have to pin down disk driver and I/O paths for
> example). Linux prefers to try to keep simple debuggable approaches to
> things.
You could do it. Start with kmalloc_pageable (probably actually
vmalloc_pageable) and introduce new sections for pageable data and text,
which can be marked just as init sections are currently. Introduce it
slowly, adding it a little at a time like we did SMP, and like we _should_
have done preemption.
It's debatable what kind of benefit it would give you over and above just
fixing specific cases like page tables, though. Most of the systems where
I've _really_ cared about RAM to that extent have been systems without any
local storage which could sanely be used for swap.
--
dwmw2
next prev parent reply other threads:[~2002-07-27 16:22 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
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 [this message]
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=16918.1027787098@redhat.com \
--to=dwmw2@infradead.org \
--cc=alan@lxorguk.ukuu.org.uk \
--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.