From: Samuel Thibault <samuel.thibault@eu.citrix.com>
To: qemu-devel@nongnu.org
Cc: Markus Hitter <mah@jump-ing.de>
Subject: Re: [Qemu-devel] [PATCH 2/2 v2] Direct IDE I/O
Date: Mon, 3 Dec 2007 20:26:48 +0100 [thread overview]
Message-ID: <20071203192648.GD3797@implementation> (raw)
In-Reply-To: <200712031539.49285.paul@codesourcery.com>
Paul Brook, le Mon 03 Dec 2007 15:39:48 +0000, a écrit :
> I think host caching is still useful enough to be enabled by default, and
> provides a significant performance increase in several cases.
>
> - The guest typically has a relatively small quantity of RAM, compared to a
> modern machine. Allowing the host OS to act as a demand-based L2 cache
> allows this to be used without having to dedicate excessive quantities of ram
> to qemu.
> - I've seen reports that it significantly speeds up the windows installer.
> - Host cache is persistent between multiple qemu runs. f you're doing anything
> that requires frequent guest reboots (e.g. kernel debugging) this is going to
> be a huge win.
> - You're running a host OS that has limited or no caching (e.g. DOS).
Yes, and in other cases (e.g. real-production KVM/Xen servers), this is
just cache duplication.
> I'd hope that the host OS would have cache use heuristics that would help
> limit cache pollution.
How could it? It can't detect that the guest also has a buffer/page
cache.
Samuel
next prev parent reply other threads:[~2007-12-03 19:26 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-03 10:09 [Qemu-devel] [PATCH 0/2 v2] Open disk images with O_DIRECT Laurent Vivier
2007-12-03 10:09 ` [Qemu-devel] [PATCH 1/2 v2] Add "cache" parameter to "-drive" Laurent Vivier
2007-12-03 10:09 ` [Qemu-devel] [PATCH 2/2 v2] Direct IDE I/O Laurent Vivier
2007-12-03 10:23 ` Fabrice Bellard
2007-12-03 10:30 ` Laurent Vivier
2007-12-03 11:40 ` Markus Hitter
2007-12-03 15:39 ` Paul Brook
2007-12-03 19:26 ` Samuel Thibault [this message]
2007-12-03 15:54 ` Anthony Liguori
2007-12-03 17:08 ` Samuel Thibault
2007-12-03 17:17 ` Paul Brook
2007-12-03 17:49 ` Jamie Lokier
2007-12-03 18:08 ` Anthony Liguori
2007-12-03 18:40 ` Jamie Lokier
2007-12-03 18:06 ` Anthony Liguori
2007-12-03 19:10 ` Laurent Vivier
2007-12-03 19:16 ` Paul Brook
2007-12-03 21:36 ` Anthony Liguori
2007-12-04 12:49 ` Gerd Hoffmann
2007-12-04 13:02 ` Laurent Vivier
2007-12-04 8:13 ` Laurent Vivier
2007-12-03 21:13 ` Gerd Hoffmann
2007-12-03 21:23 ` Samuel Thibault
2007-12-03 21:38 ` Anthony Liguori
2007-12-04 13:21 ` Gerd Hoffmann
2007-12-04 15:03 ` Anthony Liguori
2007-12-04 16:18 ` Gerd Hoffmann
2007-12-05 14:47 ` Anthony Liguori
2007-12-03 19:14 ` Paul Brook
2007-12-03 19:00 ` Laurent Vivier
2007-12-03 11:14 ` Johannes Schindelin
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=20071203192648.GD3797@implementation \
--to=samuel.thibault@eu.citrix.com \
--cc=mah@jump-ing.de \
--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).