From: Steve Ofsthun <sofsthun@virtualiron.com>
To: "P M, Priya (STSD)" <pm.priya@hp.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Performance on QEMU IDE disks
Date: Fri, 14 Jul 2006 15:41:23 -0400 [thread overview]
Message-ID: <44B7F363.1050106@virtualiron.com> (raw)
In-Reply-To: <EC1A9FC8C953C34EA0DB9151F00D6D7786D38F@BGEEXC07.asiapacific.cpqcorp.net>
P M, Priya (STSD) wrote:
> We have disabled the Write Cache using sdparm and hdparm utilities. But
> if you see the results in Linux Full Virtualization, the Sequential
> Write IOPs are better than Native performance. I am wondering how is
> this possible? Is there anywhere the caching is happening in the full
> virtualization case? If you have an idea about this behavior, please let
> me know.
QEMU does indeed use the buffer cache in Domain 0. In doing so, it also
will take advantage of Domain 0 read ahead/write behind. The down side is
that the disk write ordering guarantees expected by DomU filesystems are
violated as well. If XEN or Domain 0 crashes, your DomU filesystems may
be toast.
To fix this you would need to patch QEMU to used O_DIRECT when accessing
the virtual disk backing store object (block device, file, etc). We are
currently testing just such a patch for the old QEMU device model. I
haven't looked at the new device model to see if it already handles this.
Steve
--
Steve Ofsthun - Virtual Iron Software, Inc.
next prev parent reply other threads:[~2006-07-14 19:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-14 16:24 Performance on QEMU IDE disks P M, Priya (STSD)
2006-07-14 19:41 ` Steve Ofsthun [this message]
2006-07-18 14:49 ` Stephen Tweedie
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=44B7F363.1050106@virtualiron.com \
--to=sofsthun@virtualiron.com \
--cc=pm.priya@hp.com \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.