From: Paul Brook <paul@codesourcery.com>
To: Rik van Riel <riel@redhat.com>
Cc: alan@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [RFC][PATCH] make sure disk writes actually hit disk
Date: Fri, 28 Jul 2006 22:01:08 +0100 [thread overview]
Message-ID: <200607282201.09092.paul@codesourcery.com> (raw)
In-Reply-To: <44CA76E6.4050702@redhat.com>
> > Have you measured the impact of O_SYNC? I wouldn't be surprised if it was
> > significant.
>
> I suspect it'll be horrific in the qemu codebase (blocking execution
> of the guest OS until disk IO is complete), but it's fine in the Xen
> qemu-dm situation, where IO completion happens asynchronously.
>
> The recent commit message on the Xen side did not suggest there was
> that much of a difference between both qemu code bases. Obviously
> I was wrong, and the O_SYNC bandaid should probably be kept out for
> now.
Ah, ok. I didn't realise they'd diverged that much either.
Paul
next prev parent reply other threads:[~2006-07-28 21:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-28 19:54 [Qemu-devel] [RFC][PATCH] make sure disk writes actually hit disk Rik van Riel
2006-07-28 19:58 ` [Qemu-devel] " Rik van Riel
2006-07-28 20:12 ` Anthony Liguori
2006-07-28 20:18 ` Rik van Riel
2006-07-28 20:30 ` Paul Brook
2006-07-28 20:43 ` Rik van Riel
2006-07-28 21:01 ` Paul Brook [this message]
2006-07-31 7:08 ` Jens Axboe
2006-07-29 9:57 ` [Qemu-devel] " Fabrice Bellard
2006-07-29 14:59 ` Rik van Riel
2006-07-29 16:04 ` Paul Brook
2006-07-29 16:22 ` Rik van Riel
2006-07-29 16:31 ` Paul Brook
2006-07-31 7:08 ` Jens Axboe
2006-07-29 17:33 ` Bill C. Riemers
2006-07-30 21:47 ` Jamie Lokier
2006-07-30 21:41 ` Jamie Lokier
2006-07-31 9:52 ` andrzej zaborowski
2006-07-31 10:17 ` Jens Axboe
2006-07-31 17:50 ` andrzej zaborowski
2006-07-31 7:08 ` Jens Axboe
2006-07-31 7:56 ` Jonas Maebe
2006-07-31 8:18 ` Jens Axboe
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=200607282201.09092.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=alan@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=riel@redhat.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 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).