From: Ralf Baechle <ralf@uni-koblenz.de>
To: Santosh Eraniose <santosh@sony.co.in>
Cc: Linux-MM@kvack.org
Subject: Re: Memory partitioning
Date: Mon, 4 Sep 2000 09:51:57 +0200 [thread overview]
Message-ID: <20000904095157.A1186@bacchus.dhis.org> (raw)
In-Reply-To: <4.3.2.7.0.20000822155755.00aa3e00@192.168.1.9>; from santosh@sony.co.in on Tue, Aug 22, 2000 at 04:02:51PM +0530
On Tue, Aug 22, 2000 at 04:02:51PM +0530, Santosh Eraniose wrote:
> Is it possible to partition the MMU such that multiple OS
> can run on the same platform.
> In all examples I see like MKLinux , the mem mgmt of Linux is mapped to the
> underlying Mach kernel.
> The other extreme is as in RTAI (Real time App Interface), where the MMU is
> handled by linux, but the
> scheduling is done by RTAI.
Several approaches:
- IBM S390 can partition the hardware. In cooperation with IBM's VM this
allows to completly - and efficiently - subdivide the machine into multiple
virtual machines. VMs can even nest.
- Less perfect due to not available VM-like software and no support of the
hardware as on the S390 for example Sun's E10000 or SGI Origin 2000/3000
offer partitioning. This style of partitioning is mostly implemented
by the hardware of the machines.
The two approaches guarantee that even a virtual machine or partition that goes nuts can't crash another virtual machine or partition.
- Not implemented but in theory implementable would be multiple kernels
running on top RTLinux's realtime kernel.
Ralf
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
next prev parent reply other threads:[~2000-09-04 7:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-22 10:32 Santosh Eraniose
2000-09-04 7:51 ` Ralf Baechle [this message]
2000-08-22 13:18 Mark_H_Johnson
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=20000904095157.A1186@bacchus.dhis.org \
--to=ralf@uni-koblenz.de \
--cc=Linux-MM@kvack.org \
--cc=santosh@sony.co.in \
/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