From: Tom Vier <tmv@comcast.net>
To: Reiserfs List <reiserfs-list@namesys.com>
Subject: Re: write barrier patches for 2.4.21
Date: Thu, 28 Aug 2003 20:07:30 -0400 [thread overview]
Message-ID: <20030829000730.GA9019@zero> (raw)
In-Reply-To: <20030828170725.GB21352@matchmail.com>
On Thu, Aug 28, 2003 at 10:07:25AM -0700, Mike Fedyk wrote:
> On Wed, Aug 27, 2003 at 08:37:40PM -0400, Chris Mason wrote:
> > 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.
>
> So, in essence, TCQ is exposing what is happening in the cache, and allowing
> control/showing state compared to IDE's non-TCQ write cache. Do I have that
> right?
i'm not sure what you mean. chris is just saying tcq makes performance w/o
write cache better. i WOULD like to see wb's used w/ scsi. it would be nice
to be able to safely enable write cache on my drives.
--
Tom Vier <tmv@comcast.net>
DSA Key ID 0xE6CB97DA
next prev parent reply other threads:[~2003-08-29 0:07 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
2003-08-28 17:07 ` Mike Fedyk
2003-08-29 0:07 ` Tom Vier [this message]
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=20030829000730.GA9019@zero \
--to=tmv@comcast.net \
--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 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.