From: Disconnect <lkml@sigkill.net>
To: Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: RFC: pageable kernel-segments
Date: Tue, 17 Apr 2001 12:07:56 -0400 [thread overview]
Message-ID: <20010417120756.C11536@sigkill.net> (raw)
In-Reply-To: <27525795B28BD311B28D00500481B7601F11D9@ftrs1.intranet.ftr.nl>
In-Reply-To: <27525795B28BD311B28D00500481B7601F11D9@ftrs1.intranet.ftr.nl>
On Tue, 17 Apr 2001, Heusden, Folkert van did have cause to say:
> I would think is usable (for example) for my 8MB ram laptop.
> Anyone any thoughts on this?
I'm not a kernel hacker, but I've got some thoughts on this:
1> Modules (with the autoloader) can do that for anything not necessary to
boot. (Although even modules could lose a few pages after they
load/init/etc. Hardware setup tends to only happen once..)
2> It'd be great for embedded systems. But you'd need a "scale" -
something along the lines of "Page this out, compress it, step on it,
forget it, we'll never need it in a hurry" up through "page this out if
you -absolutely- have to, but make it easily accessible as fast as
possible".
3> It would involve a major kernel rewrite before it was anything more
than a slowdown to a few drivers supporting it. And there would probably
need to be some /proc method of forbidding paging on certain
(modules/segments/etc) so that, for example, people who hit the
least-likely-path (most-likely-to-page-out) on a regular basis can disable
paging of that section/module/driver/whatnot.
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1 [www.ebb.org/ungeek]
GIT/CC/CM/AT d--(-)@ s+:-- a-->? C++++$ ULBS*++++$ P+>+++ L++++>+++++
E--- W+++ N+@ o+>$ K? w--->+++++ O- M V-- PS+() PE Y+@ PGP++() t 5---
X-- R tv+@ b++++>$ DI++++ D++(+++) G++ e* h(-)* r++ y++
------END GEEK CODE BLOCK------
next prev parent reply other threads:[~2001-04-17 16:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-17 15:57 RFC: pageable kernel-segments Heusden, Folkert van
2001-04-17 16:07 ` Disconnect [this message]
[not found] ` <01041720013700.02396@idun>
2001-04-20 13:41 ` Disconnect
2001-04-17 19:21 ` H. Peter Anvin
2001-04-17 23:58 ` Albert D. Cahalan
2001-04-20 12:13 ` Stephen C. Tweedie
2001-04-20 14:23 ` Venkatesh Ramamurthy
2001-04-20 14:49 ` Alan Cox
2001-04-20 15:40 ` Venkatesh Ramamurthy
2001-04-20 18:51 ` Stephen C. Tweedie
2001-04-21 15:48 ` Rik van Riel
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=20010417120756.C11536@sigkill.net \
--to=lkml@sigkill.net \
--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