public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: Andreas Dilger <adilger@clusterfs.com>
Cc: Linus Torvalds <torvalds@transmeta.com>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [patch 9/16] direct-to-BIO writeback for writeback-mode ext3
Date: Sat, 01 Jun 2002 13:14:21 -0700	[thread overview]
Message-ID: <3CF92B1D.E466B743@zip.com.au> (raw)
In-Reply-To: <3CF88903.E253A075@zip.com.au> <20020601191514.GA7905@turbolinux.com>

Andreas Dilger wrote:
> 
> On Jun 01, 2002  01:42 -0700, Andrew Morton wrote:
> > Turn on direct-to-BIO writeback for ext3 in data=writeback mode.
> 
> A minor note on this (especially minor since I believe data=journal
> doesn't even work in 2.5), but you should probably also change the
> address ops in ext3/ioctl.c if you enable/disable per-inode data
> journaling.

hrm.  Actually, changing journalling mode against a file while
modifications are happening against it is almost certain to explode
if the timing is right.  ISTR that we have seen bug reports against
this on ext3-users.  This is just waaaay too hard to do.

But we can fix it by doing the opposite: create three separate
a_ops instances, one for each journalling mode.  Assign it at
new_inode/read_inode time.

This way, we don't have to do the `ext3_should_journal_data()'
tests all over the place and we just don't care if someone diddles
the journalling mode while the file is otherwise in use.

Another one for my todo list..

-

  reply	other threads:[~2002-06-01 20:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-01  8:42 [patch 9/16] direct-to-BIO writeback for writeback-mode ext3 Andrew Morton
2002-06-01 19:15 ` Andreas Dilger
2002-06-01 20:14   ` Andrew Morton [this message]
2002-06-01 20:51     ` Andreas Dilger

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=3CF92B1D.E466B743@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=adilger@clusterfs.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox