All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <clm@fb.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: <linux-fsdevel@vger.kernel.org>,
	Ext4 Developers List <linux-ext4@vger.kernel.org>,
	<xfs@oss.sgi.com>, <linux-btrfs@vger.kernel.org>,
	"Theodore Ts'o" <tytso@mit.edu>
Subject: Re: [PATCH 1/4] fs: split update_time() into update_time() and write_time()
Date: Fri, 21 Nov 2014 15:08:48 -0500	[thread overview]
Message-ID: <1416600528.24312.10@mail.thefacebook.com> (raw)
In-Reply-To: <1416599964-21892-2-git-send-email-tytso@mit.edu>

On Fri, Nov 21, 2014 at 2:59 PM, Theodore Ts'o <tytso@mit.edu> wrote:
> In preparation for adding support for the lazytime mount option, we
> need to be able to separate out the update_time() and write_time()
> inode operations.  Currently, only btrfs and xfs uses update_time().
> 
> We needed to preserve update_time() because btrfs wants to have a
> special btrfs_root_readonly() check; otherwise we could drop the
> update_time() inode operation entirely.

No objections here, I'll give the queue a whirl.  You can add my 
acked-by-or-Ill-fix-whatever-breaks

I look forward to the patch that makes us all lazy by default.

-chris




WARNING: multiple messages have this Message-ID (diff)
From: Chris Mason <clm@fb.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: linux-fsdevel@vger.kernel.org,
	Ext4 Developers List <linux-ext4@vger.kernel.org>,
	linux-btrfs@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: [PATCH 1/4] fs: split update_time() into update_time() and write_time()
Date: Fri, 21 Nov 2014 15:08:48 -0500	[thread overview]
Message-ID: <1416600528.24312.10@mail.thefacebook.com> (raw)
In-Reply-To: <1416599964-21892-2-git-send-email-tytso@mit.edu>

On Fri, Nov 21, 2014 at 2:59 PM, Theodore Ts'o <tytso@mit.edu> wrote:
> In preparation for adding support for the lazytime mount option, we
> need to be able to separate out the update_time() and write_time()
> inode operations.  Currently, only btrfs and xfs uses update_time().
> 
> We needed to preserve update_time() because btrfs wants to have a
> special btrfs_root_readonly() check; otherwise we could drop the
> update_time() inode operation entirely.

No objections here, I'll give the queue a whirl.  You can add my 
acked-by-or-Ill-fix-whatever-breaks

I look forward to the patch that makes us all lazy by default.

-chris



_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2014-11-21 20:09 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-21 19:59 [PATCH 0/4] add support for a lazytime mount option Theodore Ts'o
2014-11-21 19:59 ` Theodore Ts'o
2014-11-21 19:59 ` [PATCH 1/4] fs: split update_time() into update_time() and write_time() Theodore Ts'o
2014-11-21 19:59   ` Theodore Ts'o
2014-11-21 20:08   ` Chris Mason [this message]
2014-11-21 20:08     ` Chris Mason
2014-11-21 21:42     ` Theodore Ts'o
2014-11-21 21:42       ` Theodore Ts'o
2014-11-24 16:38       ` David Sterba
2014-11-24 16:38         ` David Sterba
2014-11-24 17:22         ` Theodore Ts'o
2014-11-24 17:22           ` Theodore Ts'o
2014-11-24 18:09           ` David Sterba
2014-11-24 18:09             ` David Sterba
2014-11-24 15:21   ` Christoph Hellwig
2014-11-24 15:21     ` Christoph Hellwig
2014-11-24 15:56     ` Theodore Ts'o
2014-11-24 15:56       ` Theodore Ts'o
2014-11-24 17:34     ` David Sterba
2014-11-24 17:34       ` David Sterba
2014-11-25 15:51       ` David Sterba
2014-11-25 15:51         ` David Sterba
2014-11-25 17:01         ` Christoph Hellwig
2014-11-21 19:59 ` [PATCH 2/4] vfs: add support for a lazytime mount option Theodore Ts'o
2014-11-21 19:59   ` Theodore Ts'o
2014-11-25  1:52   ` Dave Chinner
2014-11-25  1:52     ` Dave Chinner
2014-11-25  4:33     ` Theodore Ts'o
2014-11-25  4:33       ` Theodore Ts'o
2014-11-25 15:32       ` Boaz Harrosh
2014-11-25 15:32         ` Boaz Harrosh
2014-11-25 17:19       ` Jan Kara
2014-11-25 17:19         ` Jan Kara
2014-11-25 17:57         ` Theodore Ts'o
2014-11-25 17:57           ` Theodore Ts'o
2014-11-25 20:18           ` Jan Kara
2014-11-25 20:18             ` Jan Kara
2014-11-25 17:30       ` Jan Kara
2014-11-25 17:30         ` Jan Kara
2014-11-25 19:26         ` Theodore Ts'o
2014-11-25 19:26           ` Theodore Ts'o
2014-11-26  0:24       ` Dave Chinner
2014-11-26  0:24         ` Dave Chinner
2014-11-21 19:59 ` [PATCH 3/4] vfs: don't let the dirty time inodes get more than a day stale Theodore Ts'o
2014-11-21 19:59   ` Theodore Ts'o
2014-11-21 20:19   ` Andreas Dilger
2014-11-21 20:19     ` Andreas Dilger
2014-11-21 21:36     ` Theodore Ts'o
2014-11-21 21:36       ` Theodore Ts'o
2014-11-21 23:09       ` Andreas Dilger
2014-11-25  1:53   ` Dave Chinner
2014-11-25  1:53     ` Dave Chinner
2014-11-25  4:45     ` Theodore Ts'o
2014-11-25  4:45       ` Theodore Ts'o
2014-11-25 23:48       ` Dave Chinner
2014-11-25 23:48         ` Dave Chinner
2014-11-26 10:20         ` Theodore Ts'o
2014-11-26 10:20           ` Theodore Ts'o
2014-11-26 22:39           ` Dave Chinner
2014-11-26 22:39             ` Dave Chinner
2014-11-25 17:31   ` Jan Kara
2014-11-25 17:31     ` Jan Kara
2014-11-21 19:59 ` [PATCH 4/4] ext4: add support for a lazytime mount option Theodore Ts'o
2014-11-21 19:59   ` Theodore Ts'o
2014-11-25 17:34   ` Jan Kara
2014-11-25 17:34     ` Jan Kara

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=1416600528.24312.10@mail.thefacebook.com \
    --to=clm@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=tytso@mit.edu \
    --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.