mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Florian Weimer <Florian.Weimer@RUS.Uni-Stuttgart.DE>
To: linux-kernel@vger.kernel.org
Subject: Re: Disk hardware caching, performance, and journalling
Date: 24 Nov 2001 20:39:12 +0100	[thread overview]
Message-ID: <tgoflsez6n.fsf@mercury.rus.uni-stuttgart.de> (raw)
In-Reply-To: <3BFFE8A2.1010708@rueb.com> <3BFFF021.D963B467@zip.com.au>
In-Reply-To: <3BFFF021.D963B467@zip.com.au> (Andrew Morton's message of "Sat, 24 Nov 2001 11:08:17 -0800")

Andrew Morton <akpm@zip.com.au> writes:

> 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.  But given that the journal is, we hope, a strictly
> ascending and (we really hope) contiguous chunk of blocks, it's
> quite unlikely that the disk will decide to write them in an
> unexpected order.  This is especially true if the journal was
> created when the disk was relatively unfragmented.

When the journal resides on multiple disks or disks different from the
actual data (think LVM or RAID), all bets are off.  You need
synchronous write operations in these cases, I think.

-- 
Florian Weimer 	                  Florian.Weimer@RUS.Uni-Stuttgart.DE
University of Stuttgart           http://cert.uni-stuttgart.de/
RUS-CERT                          +49-711-685-5973/fax +49-711-685-5898

  reply	other threads:[~2001-11-24 19:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-24 18:36 Steve Bergman
2001-11-24 19:08 ` Andrew Morton
2001-11-24 19:39   ` Florian Weimer [this message]
2001-11-24 21:57   ` Phil Howard
2001-11-25  9:22   ` Chris Wedgwood
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=tgoflsez6n.fsf@mercury.rus.uni-stuttgart.de \
    --to=florian.weimer@rus.uni-stuttgart.de \
    --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

all inboxes | Powered by JetHome®