From: Eric Sandeen <sandeen@sandeen.net>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: Andi Kleen <andi-suse@firstfloor.org>,
linux-kernel@vger.kernel.org, xfs@oss.sgi.com,
Andi Kleen <andi@firstfloor.org>,
Alasdair G Kergon <agk@redhat.com>, Milan Broz <mbroz@redhat.com>
Subject: Re: Device loses barrier support
Date: Thu, 04 Dec 2008 21:26:57 -0600 [thread overview]
Message-ID: <49389F81.1090306@sandeen.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0812041401210.23079@hs20-bc2-1.build.redhat.com>
Mikulas Patocka wrote:
> Another thing:
>
> I'm wondering, where in fsync() does Linux wait for hardware disk cache to
> be flushed? Isn't there a bug that fsync() will return before the cache is
> flushed? I couldn't really find it. The last thing do_fsync calls is
> filemap_fdatawait and it doesn't do cache flush (blkdev_issue_flush).
ext4, reiserfs, and xfs all call blkdev_issue_flush() in their ->fsync
file operations (or down that path).
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
WARNING: multiple messages have this Message-ID (diff)
From: Eric Sandeen <sandeen@sandeen.net>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: Andi Kleen <andi@firstfloor.org>, Milan Broz <mbroz@redhat.com>,
Andi Kleen <andi-suse@firstfloor.org>,
linux-kernel@vger.kernel.org, Alasdair G Kergon <agk@redhat.com>,
xfs@oss.sgi.com
Subject: Re: Device loses barrier support
Date: Thu, 04 Dec 2008 21:26:57 -0600 [thread overview]
Message-ID: <49389F81.1090306@sandeen.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0812041401210.23079@hs20-bc2-1.build.redhat.com>
Mikulas Patocka wrote:
> Another thing:
>
> I'm wondering, where in fsync() does Linux wait for hardware disk cache to
> be flushed? Isn't there a bug that fsync() will return before the cache is
> flushed? I couldn't really find it. The last thing do_fsync calls is
> filemap_fdatawait and it doesn't do cache flush (blkdev_issue_flush).
ext4, reiserfs, and xfs all call blkdev_issue_flush() in their ->fsync
file operations (or down that path).
-Eric
next prev parent reply other threads:[~2008-12-05 3:27 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0812040009340.15169@hs20-bc2-1.build.redhat.com>
[not found] ` <20081204100050.GN6703@one.firstfloor.org>
2008-12-04 14:00 ` Device loses barrier support (was: Fixed patch for simple barriers.) Mikulas Patocka
2008-12-04 14:00 ` Mikulas Patocka
2008-12-04 14:20 ` Andi Kleen
2008-12-04 14:20 ` Andi Kleen
2008-12-04 14:17 ` Mikulas Patocka
2008-12-04 14:17 ` Mikulas Patocka
2008-12-04 14:58 ` Andi Kleen
2008-12-04 14:58 ` Andi Kleen
2008-12-04 16:45 ` Mikulas Patocka
2008-12-04 16:45 ` Mikulas Patocka
2008-12-04 17:48 ` Andi Kleen
2008-12-04 17:48 ` Andi Kleen
2008-12-04 17:53 ` Christoph Hellwig
2008-12-04 17:53 ` Christoph Hellwig
2008-12-04 19:37 ` Mikulas Patocka
2008-12-04 19:37 ` Mikulas Patocka
2008-12-04 22:15 ` Andi Kleen
2008-12-04 22:15 ` Andi Kleen
2008-12-04 23:08 ` Mikulas Patocka
2008-12-04 23:08 ` Mikulas Patocka
2008-12-05 0:48 ` Andi Kleen
2008-12-05 0:48 ` Andi Kleen
2008-12-05 1:16 ` Mikulas Patocka
2008-12-05 1:16 ` Mikulas Patocka
2008-12-05 1:37 ` Andi Kleen
2008-12-05 1:37 ` Andi Kleen
2008-12-05 2:21 ` Mikulas Patocka
2008-12-05 2:21 ` Mikulas Patocka
2008-12-05 3:09 ` Andi Kleen
2008-12-05 3:09 ` Andi Kleen
2008-12-05 11:52 ` Alan Cox
2008-12-05 11:52 ` Alan Cox
2008-12-05 12:29 ` Andi Kleen
2008-12-05 12:29 ` Andi Kleen
2008-12-05 3:26 ` Eric Sandeen [this message]
2008-12-05 3:26 ` Device loses barrier support Eric Sandeen
2008-12-07 4:17 ` Device loses barrier support (was: Fixed patch for simple barriers.) Dave Chinner
2008-12-07 4:17 ` Dave Chinner
2008-12-05 5:44 ` Device loses barrier support Timothy Shimmin
2008-12-05 5:44 ` Timothy Shimmin
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=49389F81.1090306@sandeen.net \
--to=sandeen@sandeen.net \
--cc=agk@redhat.com \
--cc=andi-suse@firstfloor.org \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbroz@redhat.com \
--cc=mpatocka@redhat.com \
--cc=xfs@oss.sgi.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.