From: Tiger Yang <tiger.yang@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 0/2] support strictatime in ocfs2
Date: Wed, 02 Mar 2011 19:27:16 +0800 [thread overview]
Message-ID: <4D6E2994.1050302@oracle.com> (raw)
Hi, all,
As strictatime was introduced into vfs, we must support it in ocfs2.
This two patches (one for kernel, one for tools) adding support to it
and update the relative document in ocfs2.
Vfs set RELATIME by default at the beginning, so we need STRICTATIME to
clear that flag, otherwise we can not always update atime.
With strictatime, the the minimum update interval is specified by
atime_quantum, and these two options need work together.
thanks,
tiger
next reply other threads:[~2011-03-02 11:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 11:27 Tiger Yang [this message]
2011-03-02 11:30 ` [Ocfs2-devel] [PATCH 1/1] ocfs2-tools: support strictatime in ocfs2 Tiger Yang
2011-03-26 21:42 ` Joel Becker
2011-03-28 8:37 ` Tiger Yang
2011-03-02 11:32 ` [Ocfs2-devel] [PATCH 1/1] ocfs2: clean up mount option about atime in ocfs2.txt Tiger Yang
2011-03-26 21:44 ` Joel Becker
2011-03-28 8:50 ` Tiger Yang
2011-05-24 6:56 ` Joel Becker
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=4D6E2994.1050302@oracle.com \
--to=tiger.yang@oracle.com \
--cc=ocfs2-devel@oss.oracle.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;
as well as URLs for NNTP newsgroup(s).