From: "Nicholas E. Walker" <new@vernix.org>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Re: V=R
Date: Sun, 11 Apr 2004 13:17:22 -0400 [thread overview]
Message-ID: <20040411171722.GI1297@vernix.org> (raw)
In-Reply-To: <20040410145043.GA28734@bakunin.copyleft.de>
On Sat, Apr 10, 2004 at 04:50:43PM +0200, Michael Koehne wrote:
> this reminds me on VM's V=R nucleus option. A V=R is a memory partition
> dedicated to 1 user, e.g. an MVS guest running under VM who is doing its
> own demand paging. To translate this to Linux could be the following :
>
> e.g. a system with 1GB real ram could boot `linux mem=256m` with
> only a quarter of ram for the hosting system. We now need two tricks:
>
> 1: add 768m of ram as V=R memory (dont use it for Linux processes,
> buffers, ...) partition and offer it as /dev/v=r. (this would
> be a host kernel patch)
>
> 2: use this V=R region for UML `linux mem=256m@256m` (this would
> be a user kernel patch)
>
> I dont know how difficult implementation would be, but I think most
> of an UML V=R is already there. The real V=R is vice versa, so VM
> is running in upper core, to offer the lower core to the one and
> only guest a virtual=real environment.
You could try using the NVRD (non-volatile ram disk) driver to acheive
this. It creates /dev/nvrd0 out of all memory not allocated by the
kernel.
http://www.savan.com/erez/v2.4.16-rmk1-hh15/nvrd.c
It's not as efficient as it could be because it is designed to allow for
enlarging the ram disk (so it puts the first block at the highest memory
address, all addresses are reversed). This is sort of useless in a
system where RAM is volatile..
Nicholas
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2004-04-11 17:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.59.9.0404091209570.10714@hathi.bw-networx.net>
[not found] ` <185d01c41e23$5996cc00$2000000a@schlepptopp>
2004-04-09 12:47 ` [uml-devel] Re: [uml-user] Network lags roland
2004-04-09 16:26 ` Jeff Dike
2004-04-09 18:33 ` [uml-devel] uml responsivenes or "AS vs DEADLINE Scheduler on uml-host" - was: " roland
2004-04-10 12:28 ` BlaisorBlade
2004-04-13 21:26 ` roland
2004-04-14 1:02 ` Henrik Nordstrom
[not found] ` <c58kbu$el1$1@sea.gmane.org>
2004-04-10 14:08 ` [uml-devel] " Jeff Dike
2004-04-10 14:00 ` Sven Köhler
2004-04-10 17:07 ` Jeff Dike
2004-04-10 21:22 ` Sven Köhler
2004-04-10 23:29 ` Henrik Nordstrom
2004-04-11 3:45 ` attriel
2004-04-15 0:31 ` roland
2004-04-15 12:01 ` David Cannings
[not found] ` <407EADE0.8010308@cox.net>
2004-04-15 21:11 ` roland
2004-04-16 15:12 ` Matthew Bloch
2004-04-18 10:54 ` roland
2004-04-10 14:50 ` [uml-devel] Re: V=R Michael Koehne
2004-04-11 16:54 ` BlaisorBlade
2004-04-11 17:17 ` Nicholas E. Walker [this message]
2004-04-10 15:12 ` [uml-devel] Re: [uml-user] Network lags Nicholas E. Walker
2004-04-10 16:46 ` Steven Pritchard
2004-04-10 23:41 ` Henrik Nordstrom
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=20040411171722.GI1297@vernix.org \
--to=new@vernix.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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.