From: "Sven Köhler" <skoehler@upb.de>
To: Jeff Dike <jdike@addtoit.com>
Cc: user-mode-linux-user@lists.sourceforge.net,
user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Re: [uml-user] Network lags
Date: Sat, 10 Apr 2004 23:22:44 +0200 [thread overview]
Message-ID: <407865A4.4070403@upb.de> (raw)
In-Reply-To: <20040410170707.GA6492@ccure.user-mode-linux.org>
>>what's so bad about it?
>
> It can put the host at risk. There's a VM system for a reason, and it needs
> swap in order to be able to back out of memory shortages. mlocking large
> amounts of memory subverts that and increases the possibility of deadlocking.
good point, but mlocking 128M should be like running the host with 128M
less. so if i could tell the kernel not to touch a certain memory-area
on the append-line, should there still be any VM issues?
of course that would need further patching of the host-kernel so that
UML can access and manage the reserved memory.
>>well, what do you mean with managing the host memory? will be some kind
>>tool or built-in option of the UML-kernel?
>
> Both. There is pluggable memory in UML, and a tool on the host to manage
> memory by moving memory between UMLs and between UMLs and the host.
sound good too, but what i have in mind is a more static thing. even if
the host goes mad and eats all the memory, i still want to be sure that
the UML-kernels have their memory region and this won't get swapped out.
-------------------------------------------------------
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 21:22 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 [this message]
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 ` [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=407865A4.4070403@upb.de \
--to=skoehler@upb.de \
--cc=jdike@addtoit.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=user-mode-linux-user@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