From: Theodore Ts'o <tytso@mit.edu>
To: Andreas Dilger <adilger@dilger.ca>
Cc: Boaz Harrosh <boaz@plexistor.com>, Jan Kara <jack@suse.cz>,
xfs@oss.sgi.com, linux-fsdevel@vger.kernel.org,
linux-ext4@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH-v5 1/5] vfs: add support for a lazytime mount option
Date: Tue, 2 Dec 2014 16:01:19 -0500 [thread overview]
Message-ID: <20141202210119.GD13618@thunk.org> (raw)
In-Reply-To: <0CAF91FD-F713-4E98-8967-9CA0390CA784@dilger.ca>
On Tue, Dec 02, 2014 at 01:37:27PM -0700, Andreas Dilger wrote:
>
> One thing that comes to mind is touch/utimes()/utimensat(). Those
> should definitely not result in timestamps being kept only in memory
> for 24h, since the whole point of those calls is to update the times.
> It makes sense for these APIs to dirty the inode for proper writeout.
Not a problem. Touch/utimes* go through notify_change() and
->setattr, so they won't go through the I_DIRTY_TIME code path.
- Ted
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2014-12-02 21:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1417154411-5367-1-git-send-email-tytso@mit.edu>
[not found] ` <1417154411-5367-2-git-send-email-tytso@mit.edu>
[not found] ` <20141128172323.GD738@quack.suse.cz>
[not found] ` <20141128181421.GA19461@google.com>
2014-12-02 12:58 ` [PATCH-v5 1/5] vfs: add support for a lazytime mount option Jan Kara
2014-12-02 17:55 ` Boaz Harrosh
2014-12-02 19:23 ` Theodore Ts'o
2014-12-02 20:37 ` Andreas Dilger
2014-12-02 21:01 ` Theodore Ts'o [this message]
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=20141202210119.GD13618@thunk.org \
--to=tytso@mit.edu \
--cc=adilger@dilger.ca \
--cc=boaz@plexistor.com \
--cc=jack@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox