From: Jamie Lokier <jamie@shareable.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] balloon driver
Date: Sun, 9 Jul 2006 04:02:17 +0100 [thread overview]
Message-ID: <20060709030215.GA10402@mail.shareable.org> (raw)
In-Reply-To: <200607090232.55272.mark.williamson@cl.cam.ac.uk>
Mark Williamson wrote:
> > Even if the guest has to swap, the reasoning is that the guest is in a
> > much better position to figure out what to swap than if the host were
> > forced to.
>
> Worse, the guest might decide to swap out a page that's already
> swapped in by the host, forcing it to be read in again only to be
> immediately written out to disk by the guest :-(
...unless the guest's disk I/O is with simulated DMA or recognisable
block-copy instruction sequences, and doesn't look at the data. In
that case the emulator can, in principle, keep track of where pages
are copied around without being examined, and avoid actually swapping
them in.
Probably not worth the complexity.
-- Jamie
next prev parent reply other threads:[~2006-07-09 3:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-05 2:58 [Qemu-devel] balloon driver Eric L
2006-07-05 14:52 ` Paul Brook
2006-07-09 1:06 ` Eric L
2006-07-09 1:32 ` Mark Williamson
2006-07-09 3:02 ` Jamie Lokier [this message]
2006-07-09 12:42 ` Mark Williamson
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=20060709030215.GA10402@mail.shareable.org \
--to=jamie@shareable.org \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).