From: Chris Mason <mason@suse.com>
To: reiserfs-list@namesys.com
Cc: linux-kernel@vger.kernel.org, axboe@suse.de
Subject: Re: [PATCH] write barriers for 2.4.x
Date: Fri, 15 Feb 2002 17:03:38 -0500 [thread overview]
Message-ID: <4193900000.1013810618@tiny> (raw)
In-Reply-To: <3728070000.1013734612@tiny>
In-Reply-To: <20020213222535.C0A45E64F2@ns1.suse.com> <3100680000.1013644053@tiny> <20020213235651.AC212E6360@ns1.suse.com> <3132400000.1013646727@tiny> <3728070000.1013734612@tiny>
[-- Attachment #1: Type: text/plain, Size: 930 bytes --]
Ok, based on input from the scsi folks, reiserfs can't safely use the
ordered tags until some error handling changes are made in the scsi
drivers. Controllers that do write back caching (with battery backup) are
a different story, and since they can still benefit from the patch, I left
the scsi support in.
In this new version, filesystems can request either ordered tags (for scsi)
or just cache flushes (for ide). The idea is to have the ide flushing on
by default in the final version, since so many people have ide drives with
write back caching on.
reiserfs now has -o barrier_tag and -o barrier_flush mount options. In
both cases, if the device doesn't support the ordering, reiserfs backs down
to unordered writes.
The attached patch is against 2.4.18-pre9, but also works against rc1. The
main target for this will be making journaled filesystems safer for IDE
users, so ide testers would be appreciated.
-chris
[-- Attachment #2: queue-barrier-6.diff.gz --]
[-- Type: application/x-gunzip, Size: 8121 bytes --]
next prev parent reply other threads:[~2002-02-15 22:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020213222535.C0A45E64F2@ns1.suse.com>
[not found] ` <3100680000.1013644053@tiny>
[not found] ` <20020213235651.AC212E6360@ns1.suse.com>
[not found] ` <3132400000.1013646727@tiny>
2002-02-15 0:56 ` [PATCH] write barriers for 2.4.x Chris Mason
2002-02-15 1:21 ` Alan Cox
2002-02-15 2:25 ` Chris Mason
2002-02-15 22:03 ` Chris Mason [this message]
2002-02-13 21:59 Chris Mason
[not found] ` <m3vgd1ufbt.fsf@merlin.emma.line.org>
2002-02-14 16:01 ` Chris Mason
2002-02-14 17:53 ` Chris Mason
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=4193900000.1013810618@tiny \
--to=mason@suse.com \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-list@namesys.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