From: James Bottomley <James.Bottomley@steeleye.com>
To: jordan.breeding@attbi.com
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: scsi write barriers (ordered tags)?
Date: 05 Feb 2003 14:24:49 -0600 [thread overview]
Message-ID: <1044476691.1775.72.camel@mulgrave> (raw)
In-Reply-To: <200302051809.NAA23237@orville.steeleye.com>
On Wed, 2003-02-05 at 11:58, jordan.breeding@attbi.com wrote:
> I understand that SCSI drives and controllers are much more
complicated than their IDE counterparts and that to implement ordered
tags in SCSI is more complicated. However, doesn't FreeBSD's CAM
layer have some kind of implementation of this which makes it safe to
use soft-updates and write back cache together?
Actually, no. The problem that caches cause is that they cache data,
not transactions. You can force the caches to respect transaction order
by flushing them, but that gets expensive.
I thought that I read that sometime ago but I have been trying to
find references to it on google this morning and couldn't find any.
I guess what I am really after is to fold: 1) Will Linux's SCSI
layer get modified at _any_ point to support something like this to
benefit ext3/reiserfs/xfs/jfs? 2) If this will be attempted at some
point will it be later in 2.5/2.6 or will this definitely be 2.7/2.8
material? Thanks for the info and the response.
Like I said, the infrastructure exists. There's no compelling reason
to enable it (mainly because most of the benchmarks say it causes a
slowdown).
James
next parent reply other threads:[~2003-02-05 20:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200302051809.NAA23237@orville.steeleye.com>
2003-02-05 20:24 ` James Bottomley [this message]
2003-02-05 21:57 scsi write barriers (ordered tags)? berthiaume_wayne
-- strict thread matches above, loose matches on Subject: below --
2003-02-05 21:31 Cress, Andrew R
2003-02-05 16:00 Jordan Breeding
2003-02-05 16:55 ` James Bottomley
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=1044476691.1775.72.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=jordan.breeding@attbi.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox