From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
xen-devel@lists.sourceforge.net
Subject: Re: [XEN] using shmfs for swapspace
Date: Mon, 03 Jan 2005 21:06:20 +0000 [thread overview]
Message-ID: <1104785749.13302.26.camel@localhost.localdomain> (raw)
In-Reply-To: <20050103205318.GD6631@lkcl.net>
> so this tends to suggest a strategy where you allocate as
> much memory as you can afford to the DOM0 VM, and as little
> as you can afford to the guests, and make the guest swap
> files bigger to compensate.
This is essentially what the mainframe folks are already doing and have
been doing for some time because the kernel VM has no external inputs
for saying "you are virtualised so be nice"
for doing opportunistic page recycling ("I dont need this page but when
I ask for it back please tell me if you trashed the content") and for
hinting to the underlying VM what pages are best blasted out of
existance first and how to communicate so we dont page them back in
scanning them.
next prev parent reply other threads:[~2005-01-03 22:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-02 16:26 [XEN] using shmfs for swapspace Luke Kenneth Casson Leighton
2005-01-03 18:31 ` Joseph Fannin
2005-01-03 20:53 ` Luke Kenneth Casson Leighton
2005-01-03 21:06 ` Alan Cox [this message]
2005-01-04 3:04 ` [Xen-devel] " Mark Williamson
2005-01-04 14:05 ` Rik van Riel
2005-01-06 11:38 ` Luke Kenneth Casson Leighton
2005-01-05 0:11 ` Arnd Bergmann
2005-01-21 21:37 ` Rik van Riel
2005-01-26 20:56 ` Mark Williamson
2005-01-27 10:33 ` Nuutti Kotivuori
2005-01-03 21:07 ` Adam Heath
2005-01-04 9:30 ` Luke Kenneth Casson Leighton
2005-01-04 14:06 ` Rik van Riel
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=1104785749.13302.26.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lkcl@lkcl.net \
--cc=xen-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