From: Azat Khuzhin <a3at.mail@gmail.com>
To: Zach Brown <zab@zabbo.net>
Cc: Sage Weil <sweil@redhat.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-api@vger.kernel.org
Subject: Re: [PATCH RFC v2 2/2] vfs: add O_NOCMTIME
Date: Sun, 17 May 2015 00:50:30 +0300 [thread overview]
Message-ID: <20150516215030.GI11068@azat> (raw)
In-Reply-To: <1431725028-24071-3-git-send-email-zab@zabbo.net>
On Fri, May 15, 2015 at 02:23:48PM -0700, Zach Brown wrote:
> Add a O_NOCMTIME flag which prevents inode time updates on writes and
> can greatly reduce the IO overhead of writes to allocated and
> initialized regions of files.
> --- a/include/linux/fs.h
> +++ b/include/linux/fs.h
You may also want to resolve this:
/*
* Don't update ctime and mtime.
*
* Currently a special hack for the XFS open_by_handle ioctl, but we'll
* hopefully graduate it to a proper O_CMTIME flag supported by open(2) soon.
*/
#define FMODE_NOCMTIME ((__force fmode_t)0x800)
prev parent reply other threads:[~2015-05-16 21:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 21:23 [PATCH RFC v2 0/2] O_NOCMTIME protected by generic mount option Zach Brown
2015-05-15 21:23 ` [PATCH RFC v2 1/2] vfs: add generic nocmtime mount flag Zach Brown
2015-05-15 21:23 ` [PATCH RFC v2 2/2] vfs: add O_NOCMTIME Zach Brown
2015-05-16 21:50 ` Azat Khuzhin [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=20150516215030.GI11068@azat \
--to=a3at.mail@gmail.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sweil@redhat.com \
--cc=zab@zabbo.net \
/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