From: Chris Mason <mason@suse.com>
To: Peter Zaitsev <peter@mysql.com>
Cc: Jens Axboe <axboe@suse.de>, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: True fsync() in Linux (on IDE)
Date: Thu, 18 Mar 2004 15:33:21 -0500 [thread overview]
Message-ID: <1079642001.11057.7.camel@watt.suse.com> (raw)
In-Reply-To: <1079641026.2447.327.camel@abyss.local>
On Thu, 2004-03-18 at 15:17, Peter Zaitsev wrote:
> On Thu, 2004-03-18 at 12:11, Chris Mason wrote:
>
> > > I believe some missed set_page_writeback() calls caused fsync() to never
> > > really wait on anything, pretty broken... IIRC, it's fixed in latest
> > > -mm, or maybe it's just pending for next release.
> >
> > This should have only been broken in -mm. Which kernels exactly are you
> > comparing? Maybe the 3ware array defaults to different writecache
> > settings under 2.6?
>
> I'm trying RH AS 3.0 kernel, however I have the same behavior on my
> SuSE 8.2 workstation.
>
Some suse 8.2 kernels had write barriers for IDE, some did not. If
you're running any kind of recent suse kernel, you're doing cache
flushes on fsync with ext3.
Not sure if RH has ever carried the patches or not. Easy enough to test
for on suse, just look for blk_queue_ordered in the System.map.
> I use 2.6.3 kernel for tests now (It is not the latest I know)
> EXT3 file system.
>
> 3WARE has writeback cache setting in both cases.
Then it sounds like your 2.4 is doing flushes. I'd expect this test to
run very quickly without them.
-chris
next prev parent reply other threads:[~2004-03-18 20:30 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-18 1:08 True fsync() in Linux (on IDE) Peter Zaitsev
2004-03-18 6:47 ` Jens Axboe
2004-03-18 11:34 ` Matthias Andree
2004-03-18 11:55 ` Jens Axboe
2004-03-18 12:21 ` Matthias Andree
2004-03-18 12:37 ` Jens Axboe
2004-03-18 11:58 ` (no subject) Daniel Czarnecki
2004-03-18 19:44 ` True fsync() in Linux (on IDE) Peter Zaitsev
2004-03-18 19:47 ` Jens Axboe
2004-03-18 20:11 ` Chris Mason
2004-03-18 20:17 ` Peter Zaitsev
2004-03-18 20:33 ` Chris Mason [this message]
2004-03-18 20:46 ` Peter Zaitsev
2004-03-18 21:02 ` Chris Mason
2004-03-18 21:09 ` Peter Zaitsev
2004-03-18 21:19 ` Chris Mason
2004-03-19 8:05 ` Hans Reiser
2004-03-19 13:52 ` Chris Mason
2004-03-19 19:26 ` Peter Zaitsev
2004-03-19 20:23 ` Chris Mason
2004-03-19 20:31 ` Hans Reiser
2004-03-19 20:38 ` Chris Mason
2004-03-19 20:48 ` Hans Reiser
2004-03-19 20:56 ` Chris Mason
2004-03-20 11:04 ` Hans Reiser
2004-03-19 19:36 ` Hans Reiser
2004-03-19 19:57 ` Chris Mason
2004-03-19 20:04 ` Hans Reiser
2004-03-19 20:15 ` Chris Mason
2004-03-19 20:06 ` Peter Zaitsev
2004-03-19 22:03 ` Matthias Andree
2004-03-20 10:20 ` Jamie Lokier
2004-03-20 19:48 ` Peter Zaitsev
-- strict thread matches above, loose matches on Subject: below --
2004-03-22 13:08 Heikki Tuuri
2004-03-22 13:23 ` Jens Axboe
2004-03-22 15:17 ` Matthias Andree
2004-03-22 15:35 ` Christoph Hellwig
2004-03-22 19:12 ` Christoffer Hall-Frederiksen
2004-03-22 20:28 ` Matthias Andree
2004-03-22 19:33 ` Hans Reiser
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=1079642001.11057.7.camel@watt.suse.com \
--to=mason@suse.com \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@mysql.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