From: "Nicholas E. Walker" <new@vernix.org>
To: skoehler@upb.de
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Re: [uml-user] Network lags
Date: Sat, 10 Apr 2004 11:12:20 -0400 [thread overview]
Message-ID: <20040410151220.GB1297@vernix.org> (raw)
In-Reply-To: <20040410140840.GB5782@ccure.user-mode-linux.org>
On Sat, Apr 10, 2004 at 10:08:40AM -0400, Jeff Dike wrote:
> On Sat, Apr 10, 2004 at 01:06:51PM +0200, Sven K?hler wrote:
> > is there any way for the UML-kernel to allocate a non-swappable
> > memore-region in the host's memory? this could be especially important
> > for dedicated host-machines that are only to run UMLs.
>
> Yes, but there's no way I'm going to support anything like that.
>
> What I am going to do is make it possible to manage the host's memory
> so that it doesn't swap, and the UMLs in effect are mlocked.
You could try mounting ramfs on /tmp. ramfs is similar to tmpfs, except
that the contents cannot be swapped. It doesn't usefully report
used/free space, so it is somewhat problematic to have it mounted on
/tmp unless you're just running UML kernels.
However, this is sort of a misguided idea. If you have enough memory,
nothing will get swapped unless something in memory is so unused that it
would be more efficient to swap it out and use the memory for cache.
Locking the UML memory space into real memory isn't going to give you
any more memory, and increases the change that the OOM killer is going
to come out and play. So do the reasonable thing and get more memory or
run fewer UMLs.
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-10 15:12 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
2004-04-10 15:12 ` Nicholas E. Walker [this message]
2004-04-10 16:46 ` [uml-devel] Re: [uml-user] Network lags 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=20040410151220.GB1297@vernix.org \
--to=new@vernix.org \
--cc=skoehler@upb.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox