From: Jens Axboe <axboe@suse.de>
To: Greg Stark <gsstark@mit.edu>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
Jeff Garzik <jgarzik@pobox.com>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH] scsi/sata write barrier support
Date: Tue, 1 Mar 2005 09:47:42 +0100 [thread overview]
Message-ID: <20050301084741.GD12295@suse.de> (raw)
In-Reply-To: <874qg4v81q.fsf@stark.xeocode.com>
On Tue, Feb 22 2005, Greg Stark wrote:
>
> Jens Axboe <axboe@suse.de> writes:
>
> > fsync has been working all along, since the initial barrier support for
> > ide. only ext3 and reiserfs support it.
>
> Really? That's huge news. Since what kernel version(s) is that?
Since 2.6.9.
> What about a non-journaled fs, or at least a meta-data-only-journaled fs?
> Journaled FS's don't mix well with transaction based databases since they're
> basically doing their own journaling anyways.
Only works on ext3 and reiserfs currently.
--
Jens Axboe
next prev parent reply other threads:[~2005-03-01 8:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-27 12:02 [PATCH] scsi/sata write barrier support Jens Axboe
2005-01-27 15:08 ` [PATCH] scsi/sata write barrier support #2 Jens Axboe
2005-01-27 23:02 ` Jeff Garzik
2005-01-27 22:42 ` [PATCH] scsi/sata write barrier support Doug Maxey
2005-01-27 23:00 ` Jeff Garzik
2005-01-28 6:54 ` Jens Axboe
2005-01-28 8:10 ` Jeff Garzik
2005-01-28 8:18 ` Jens Axboe
2005-01-28 9:38 ` Jens Axboe
2005-01-28 13:06 ` James Bottomley
2005-01-28 13:10 ` Jens Axboe
2005-01-28 13:12 ` James Bottomley
2005-01-28 6:58 ` Jens Axboe
2005-02-22 4:42 ` Greg Stark
2005-02-22 7:13 ` Jens Axboe
2005-02-22 17:06 ` Greg Stark
2005-03-01 8:47 ` Jens Axboe [this message]
2005-03-01 15:55 ` Greg Stark
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=20050301084741.GD12295@suse.de \
--to=axboe@suse.de \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=gsstark@mit.edu \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.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.