From: "Stephen C. Tweedie" <sct@redhat.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Anders Eriksson <aer-list@mailandnews.com>,
linux-kernel@vger.kernel.org
Subject: Re: sync & asyck i/o
Date: Tue, 6 Feb 2001 18:18:08 +0000 [thread overview]
Message-ID: <20010206181808.I1167@redhat.com> (raw)
In-Reply-To: <20010206173437.A19836@redhat.com> <200102061424.PAA32284@hell.wii.ericsson.net> <E14Q9U2-0005gX-00@the-village.bc.nu> <20010206173437.A19836@redhat.com> <19450.981482081@redhat.com>
In-Reply-To: <19450.981482081@redhat.com>; from dwmw2@infradead.org on Tue, Feb 06, 2001 at 05:54:41PM +0000
Hi,
On Tue, Feb 06, 2001 at 05:54:41PM +0000, David Woodhouse wrote:
>
> sct@redhat.com said:
> > Linux will obey that if it possibly can: only in cases where the
> > hardware is actively lying about when the data has hit disk will the
> > guarantee break down.
>
> Do we attempt to ask SCSI disks nicely to flush their write caches in this
> situation? cf. http://www.danbbs.dk/~dino/SCSI/SCSI2-09.html#9.2.18
No, we simply omit to instruct them to enable write-back caching.
Linux assumes that the WCE (write cache enable) bit in a disk's
caching mode page is zero.
--Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-06 18:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-06 14:24 sync & asyck i/o Anders Eriksson
2001-02-06 14:52 ` Alan Cox
2001-02-06 17:34 ` Stephen C. Tweedie
2001-02-06 18:00 ` Ben LaHaise
2001-02-06 18:21 ` Daniel Phillips
2001-02-06 17:51 ` Josh Myer
2001-02-06 17:56 ` Alan Cox
2001-02-06 17:54 ` David Woodhouse
2001-02-06 18:18 ` Stephen C. Tweedie [this message]
2001-02-06 19:25 ` Andre Hedrick
2001-02-06 23:21 ` Stephen C. Tweedie
2001-02-07 0:42 ` Andre Hedrick
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=20010206181808.I1167@redhat.com \
--to=sct@redhat.com \
--cc=aer-list@mailandnews.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@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