From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Adam Heath <doogie@brainfood.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"xen-devel@lists.sf.net" <xen-devel@lists.sf.net>
Subject: Re: [Xen-devel] Re: [XEN] using shmfs for swapspace
Date: Tue, 4 Jan 2005 09:30:44 +0000 [thread overview]
Message-ID: <20050104093044.GC10906@lkcl.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0501031506080.21792@gradall.private.brainfood.com>
On Mon, Jan 03, 2005 at 03:07:42PM -0600, Adam Heath wrote:
> > 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.
>
> But the guest kernels need real ram to run programs in.
>
> The problem with dom0 doing the caching, is that dom0 has no idea about the
> usage pattern for the swap. It's just a plain file to dom0. Only each guest
> kernel knows how to combine swap reads/writes correctly.
... hmm...
then that tends to suggest that this is an issue that should
really be dealt with by XEN.
that there needs to be coordination of swap management between the
virtual machines.
l.
--
--
<a href="http://lkcl.net">http://lkcl.net</a>
--
next prev parent reply other threads:[~2005-01-04 9:21 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
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 [this message]
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=20050104093044.GC10906@lkcl.net \
--to=lkcl@lkcl.net \
--cc=doogie@brainfood.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.sf.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