From: Christoph Hellwig <hch@infradead.org>
To: Dan Aloni <da-x@colinux.org>
Cc: Cooperative Linux Development
<colinux-devel@lists.sourceforge.net>,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: coLinux benchmarks
Date: Mon, 5 Apr 2004 14:30:56 +0100 [thread overview]
Message-ID: <20040405143056.A5621@infradead.org> (raw)
In-Reply-To: <20040405131520.GA4395@callisto.yi.org>; from da-x@colinux.org on Mon, Apr 05, 2004 at 03:15:20PM +0200
> The VM shows better results than the host. What gives? Perhaps
> it is because of the combination of the host and guest's buffer
> cache? I'd like to know about more percise benchmarking methods
> for VMs.
How are the virtual disks for the VM implemented? If you're doing
direct I/O these numbers are indeed strange. If not OTOH that's
expected because even synchronous I/O in the guest is actually
async which makes it a lot faster.
next prev parent reply other threads:[~2004-04-05 13:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-05 13:15 Dan Aloni
2004-04-05 13:30 ` Christoph Hellwig [this message]
2004-04-05 14:05 ` Dan Aloni
2004-04-05 20:11 ` [coLinux-devel] " Eyal Lotem
2004-04-05 22:22 ` Dan Aloni
2004-04-06 13:45 ` Ian C. Blenke
2004-04-06 14:07 ` Dan Aloni
2004-04-05 23:21 ` ReactOS and CoLinux status Steven Edwards
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=20040405143056.A5621@infradead.org \
--to=hch@infradead.org \
--cc=colinux-devel@lists.sourceforge.net \
--cc=da-x@colinux.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®