From: Samuel Thibault <samuel.thibault@eu.citrix.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: marian klein <klein.marian@gmail.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"xen-discuss@opensolaris.org" <xen-discuss@opensolaris.org>
Subject: Re: IO caching on xen?
Date: Wed, 16 Jul 2008 18:46:49 +0100 [thread overview]
Message-ID: <20080716174649.GF14133@implementation.uk.xensource.com> (raw)
In-Reply-To: <20080715123253015.00000080236@djm-pc>
Dan Magenheimer, le Tue 15 Jul 2008 12:32:53 -0600, a écrit :
> > marian klein, le Tue 15 Jul 2008 11:22:05 +0000, a écrit :
> > > I am worried that the xen (or any other VM) with zvol
> > device from ZFS
> > > (or any other file system.) may remove the benefits of ZFS,
> > > because the guest OS can write something to disk but the xen itself
> > > can do some buffering
> > > or lazy writing and it may delay to write to ZFS backend.
> >
> > Xen doesn't do any kind of buffering or lazy writing. It provides
> > barriers to the guest, to ensure any needed coherency.
>
> I'm not sure if this is related or not...
>
> I was party to some internal irc where it was believed
> to be the case that when a file-backed vbd using file:'...'
> is used, dom0's page cache may contain buffer pages that
> may be inconsistent with the disk
Ah, indeed, in that case the page cache is used, and the barriers may
not have proper effect.
> whereas a file-backed vbd using tap:aio:'...' does not suffer from the
> same problem.
blktap uses O_DIRECT to avoid buffering completely indeed.
Samuel
prev parent reply other threads:[~2008-07-16 17:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-15 11:22 IO caching on xen? marian klein
2008-07-15 11:30 ` Samuel Thibault
2008-07-15 18:32 ` Dan Magenheimer
2008-07-16 17:46 ` Samuel Thibault [this message]
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=20080716174649.GF14133@implementation.uk.xensource.com \
--to=samuel.thibault@eu.citrix.com \
--cc=dan.magenheimer@oracle.com \
--cc=klein.marian@gmail.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-discuss@opensolaris.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 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.