From: Chris Wedgwood <cw@f00f.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] ide.c make write cacheing controllable by guest
Date: Mon, 25 Feb 2008 17:16:39 -0800 [thread overview]
Message-ID: <20080226011639.GA20401@puku.stupidest.org> (raw)
In-Reply-To: <20080225205040.GA18613@shareable.org>
On Mon, Feb 25, 2008 at 08:50:40PM +0000, Jamie Lokier wrote:
> On Linux (and other host OSes), fdatsync() and fsync() don't always
> commit data to hard storage; it sometimes only commits it to the hard
> drive cache.
That's a filesystem bug IMO. People should be able to use f[data]sync
with some level onf confidence or else it's basically pointless.
next prev parent reply other threads:[~2008-02-26 1:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-25 18:13 [Qemu-devel] [PATCH] ide.c make write cacheing controllable by guest Ian Jackson
2008-02-25 20:50 ` Jamie Lokier
2008-02-26 1:16 ` Chris Wedgwood [this message]
2008-02-26 7:32 ` Jamie Lokier
2008-02-26 12:15 ` Ian Jackson
2008-02-26 12:49 ` Jamie Lokier
2008-02-26 16:57 ` Ian Jackson
2008-02-26 17:25 ` Jamie Lokier
2008-02-26 18:11 ` Ian Jackson
-- strict thread matches above, loose matches on Subject: below --
2008-03-27 18:02 Ian Jackson
2008-03-27 18:16 ` Paul Brook
2008-03-28 9:38 ` Ian Jackson
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=20080226011639.GA20401@puku.stupidest.org \
--to=cw@f00f.org \
--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).