From: Lachlan McIlroy <lachlan@sgi.com>
To: David Chinner <dgc@sgi.com>
Cc: xfs-dev <xfs-dev@sgi.com>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH, RFC] Delayed logging of file sizes
Date: Mon, 26 Nov 2007 11:19:57 +1100 [thread overview]
Message-ID: <474A112D.2040006@sgi.com> (raw)
In-Reply-To: <20071125225928.GE114266761@sgi.com>
David Chinner wrote:
> On Fri, Nov 23, 2007 at 06:04:39PM +1100, Lachlan McIlroy wrote:
>> The easy solution is to log everything so that log replay doesn't need
>> to check if the on-disk version is newer - it can just replay the log.
>> But logging everything would cause too much log traffic so this patch
>> is a compromise and it logs a transaction before we flush an inode to
>> disk only if it has changes that have not yet been logged.
>
> The problem with this is that the inode will be marked dirty during the
> transaction, so we'll never be able to clean an inode if we issue a
> transaction during inode writeback.
>
Ah, yeah, good point. I wrote this patch back before that "dirty inode
on transaction" patch went in. For this transaction though the changes
to the inode have already been made (ie when we set i_update_core and
called mark_inode_dirty_sync()) so there is no need to dirty it in this
transaction. I'll keep digging. Thanks.
next prev parent reply other threads:[~2007-11-26 0:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-23 7:04 [PATCH, RFC] Delayed logging of file sizes Lachlan McIlroy
2007-11-25 22:59 ` David Chinner
2007-11-26 0:19 ` Lachlan McIlroy [this message]
2007-11-26 1:10 ` David Chinner
2007-11-26 1:29 ` Lachlan McIlroy
2007-11-26 2:15 ` David Chinner
2007-11-26 3:16 ` Lachlan McIlroy
2007-11-26 5:03 ` David Chinner
2007-11-27 3:30 ` Lachlan McIlroy
2007-11-27 10:53 ` David Chinner
2007-11-28 0:43 ` Lachlan McIlroy
2007-11-28 2:01 ` David Chinner
2007-11-28 4:18 ` Lachlan McIlroy
2007-11-28 9:07 ` David Chinner
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=474A112D.2040006@sgi.com \
--to=lachlan@sgi.com \
--cc=dgc@sgi.com \
--cc=xfs-dev@sgi.com \
--cc=xfs@oss.sgi.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.