From: Chris Mason <mason@suse.com>
To: Tom Vier <tmv@comcast.net>
Cc: Reiserfs List <reiserfs-list@namesys.com>
Subject: Re: write barrier patches for 2.4.21
Date: 27 Aug 2003 20:37:40 -0400 [thread overview]
Message-ID: <1062031059.5324.111.camel@tiny.suse.com> (raw)
In-Reply-To: <20030827220337.GB4886@zero>
On Wed, 2003-08-27 at 18:03, Tom Vier wrote:
> On Wed, Aug 27, 2003 at 10:41:03AM +0400, Oleg Drokin wrote:
> > There was a discussion about that on Kernel Summit 2003 and general opinion was that SCSI
> > does not need the WB stuff at all as it does the correct thing anyway.
>
> i found this, but no real details. do you have a better link? or could you
> tell me why scsi drives don't need wb's? afaik, they don't have nvram cache.
> so, the danger is still there, even if small (unless i'm wrong).
>
> http://lwn.net/Articles/40850/
>
scsi drives don't really need them because most scsi drives don't have
write back caching on by default, and most actually listen when you turn
the cache off. The scsi tag queuing makes good performance possible
even without writeback caching.
-chris
next prev parent reply other threads:[~2003-08-28 0:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-25 17:08 write barrier patches for 2.4.21 Gergely Tamas
2003-08-26 8:17 ` Oleg Drokin
2003-08-26 9:03 ` Gergely Tamas
2003-08-26 9:13 ` Oleg Drokin
2003-08-26 9:32 ` Gergely Tamas
2003-08-26 21:46 ` Tom Vier
2003-08-27 6:41 ` Oleg Drokin
2003-08-27 22:03 ` Tom Vier
2003-08-28 0:37 ` Chris Mason [this message]
2003-08-28 17:07 ` Mike Fedyk
2003-08-29 0:07 ` Tom Vier
2003-08-29 1:18 ` Mike Fedyk
2003-08-29 1:44 ` Chris Mason
2003-08-29 1:56 ` Matthias Andree
2003-09-02 22:10 ` Hans Reiser
2003-09-04 14:56 ` Oleg Drokin
-- strict thread matches above, loose matches on Subject: below --
2003-09-04 20:49 Tom Vier
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=1062031059.5324.111.camel@tiny.suse.com \
--to=mason@suse.com \
--cc=reiserfs-list@namesys.com \
--cc=tmv@comcast.net \
/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.