All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wedgwood <cw@f00f.org>
To: Andrew Morton <akpm@zip.com.au>
Cc: Steve Bergman <steve@rueb.com>, linux-kernel@vger.kernel.org
Subject: Re: Disk hardware caching, performance, and journalling
Date: Sun, 25 Nov 2001 22:22:14 +1300	[thread overview]
Message-ID: <20011125222214.C9672@weta.f00f.org> (raw)
In-Reply-To: <3BFFE8A2.1010708@rueb.com> <3BFFF021.D963B467@zip.com.au>
In-Reply-To: <3BFFF021.D963B467@zip.com.au>

On Sat, Nov 24, 2001 at 11:08:17AM -0800, Andrew Morton wrote:

    In theory, yes.  In my opinion, no.  For ext3, at least.  Caching
    isn't bad per-se.  It's reordering which can break the journalling
    constraints.

Some disks[1] most definately do reorder;  I've actually been able to
demonstrate this in some circumstances (it wasn't trivial to
produce and required several attempts).



  --cw

[1] SCSI, which we know does and will reorder writes when a barrier
    isn't specificed, it appears IDE drives can do the same but lack of
    hot-swap makes testing tedious :)

  parent reply	other threads:[~2001-11-25  9:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-24 18:36 Disk hardware caching, performance, and journalling Steve Bergman
2001-11-24 19:08 ` Andrew Morton
2001-11-24 19:39   ` Florian Weimer
2001-11-24 21:57   ` Phil Howard
2001-11-25  9:22   ` Chris Wedgwood [this message]
2001-11-24 19:39 ` Mark Hahn
2001-11-25  9:23   ` Chris Wedgwood
2001-11-25 21:45     ` Kevin P. Fleming
2001-11-25 22:11       ` Chris Wedgwood
2001-11-25 22:29         ` Mark Hahn
2001-11-26  1:10       ` Bernd Eckenfels
2001-11-25  9:19 ` Chris Wedgwood

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=20011125222214.C9672@weta.f00f.org \
    --to=cw@f00f.org \
    --cc=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=steve@rueb.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.