From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] [PATCH] Locking user-mode kernel RAM into host physical RAM
Date: Tue, 9 Dec 2003 20:00:45 +0100 [thread overview]
Message-ID: <200312092000.45933.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <200312081901.hB8J1VAv028738@ccure.user-mode-linux.org>
Alle 20:01, lunedì 8 dicembre 2003, Jeff Dike ha scritto:
> As far as I'm concerned, this is papering over the symptoms rather than
> fixing a real problem.
>
> If you're really not overselling memory, then the host should not be
> swapping. If it is, then that's the problem.
>
> > My experience with 2.4 as a host kernel is that it will quite happily
> > swap out pages from running applications to use as disc cache; this
> > is apparently alleviated with 2.6's "swappiness" kernel parameter.
>
> This being the case, you should maybe be looking at 2.6 as your host.
>
> > I hope that it's obvious enough to warrant inclusion in the next
> > release of the UML patch
>
> It's not. Feel free to argue, but this is really the wrong thing to do,
> IMHO.
But anyway, if the "physical memory" of the guest is not guaranted to be
actually physical, then the UML's kernel VM will get fooled. What's more,
it's the guest's VM which must decide what has to be swapped.
The only swap that must be used is the UML's one. He must be fair to his
customer(i.e. no overselling), but done that the host can't swap anything
out.
> /dev/anon is a new host driver which implements the munmap semantics needed
> by UML physical memory (pages are release to the host when they're no
> longer mapped, even if they're dirty).
It means that the guest VM will see that the available memory has shrinked and
that it will swap things out following the new memory limit? It seems to me a
little bit difficult. This (if I understand correctly) requires core VM
changes(the stock VM isn't much tested with shrinking/increasing memory
sizes, if this is supported at all, for strange architectures).
--
cat <<EOSIGN
Paolo Giarrusso, aka Blaisorblade
Linux Kernel 2.4.21/2.6.0-test on an i686; Linux registered user n. 292729
EOSIGN
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id\x1278&alloc_id371&opÌk
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2003-12-10 19:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-08 16:39 [uml-devel] [PATCH] Locking user-mode kernel RAM into host physical RAM Matthew Bloch
2003-12-08 17:31 ` Matt Ayres
2003-12-08 18:02 ` Steven Pritchard
2003-12-08 18:57 ` [uml-devel] Re: chroot option Henrik Nordstrom
2003-12-08 22:04 ` Jeff Dike
2003-12-08 23:00 ` Henrik Nordstrom
2003-12-08 19:01 ` [uml-devel] [PATCH] Locking user-mode kernel RAM into host physical RAM Jeff Dike
2003-12-08 22:23 ` Matthew Bloch
2003-12-08 23:18 ` Henrik Nordstrom
2003-12-09 0:14 ` Matthew Bloch
2003-12-09 19:00 ` BlaisorBlade [this message]
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=200312092000.45933.blaisorblade_spam@yahoo.it \
--to=blaisorblade_spam@yahoo.it \
--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