From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Gabriel Paubert <paubert@iram.es>
Cc: Tom Rini <trini@kernel.crashing.org>,
"Randy.Dunlap" <rddunlap@osdl.org>,
randy.dunlap@verizon.net,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [PATCH] move SWAP option in menu
Date: 06 Mar 2003 21:06:49 +0000 [thread overview]
Message-ID: <1046984808.18158.115.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <20030306193344.GA29166@iram.es>
On Thu, 2003-03-06 at 19:33, Gabriel Paubert wrote:
> I'd be very surprised if it were possible to have swap on a MMU-less
> machine (no virtual memory, page faults, etc.). Except for this nitpick,
> the patch looks fine, but my knowledge of MM is close to zero (and
> also of the new config language, but I'll have to learn it soon).
You can, and people have had swapping long before virtual memory. Most
ucLinux platforms can't swap because they can't dynamically relocate code.
Linux 8086 can swap because it can use CS/DS updates to relocate code/data.
The way it worked on older systems is that you never run a program which
isnt entirely in memory. With that constraint you know it won't suddenely
want data you don't have
next prev parent reply other threads:[~2003-03-06 19:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-05 4:36 [PATCH] move SWAP option in menu Randy.Dunlap
2003-03-05 18:17 ` Gabriel Paubert
2003-03-05 21:14 ` Randy.Dunlap
2003-03-06 18:43 ` Tom Rini
2003-03-06 18:49 ` Christoph Hellwig
2003-03-06 18:54 ` Tom Rini
2003-03-06 18:56 ` Christoph Hellwig
2003-03-06 19:33 ` Gabriel Paubert
2003-03-06 21:06 ` Alan Cox [this message]
2003-03-07 10:03 ` Gabriel Paubert
2003-03-07 12:41 ` Alan Cox
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=1046984808.18158.115.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=paubert@iram.es \
--cc=randy.dunlap@verizon.net \
--cc=rddunlap@osdl.org \
--cc=torvalds@transmeta.com \
--cc=trini@kernel.crashing.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).