From: Hao Li <lihao2018.fnst@cn.fujitsu.com>
To: <corbet@lwn.net>
Cc: <davem@davemloft.net>, <gregkh@linuxfoundation.org>,
<alexander.deucher@amd.com>, <mchehab+huawei@kernel.org>,
<lee.jones@linaro.org>, <ira.weiny@intel.com>,
<linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<lihao2018.fnst@cn.fujitsu.com>
Subject: [PATCH] Documentation/dax: Update description of DAX policy changing
Date: Mon, 4 Jan 2021 10:40:40 +0800 [thread overview]
Message-ID: <20210104024040.5381-1-lihao2018.fnst@cn.fujitsu.com> (raw)
After commit 77573fa310d9 ("fs: Kill DCACHE_DONTCACHE dentry even if
DCACHE_REFERENCED is set"), changes to DAX policy will take effect
as soon as all references to this file are gone.
Update the documentation accordingly.
Signed-off-by: Hao Li <lihao2018.fnst@cn.fujitsu.com>
---
Documentation/filesystems/dax.txt | 15 ++-------------
1 file changed, 2 insertions(+), 13 deletions(-)
diff --git a/Documentation/filesystems/dax.txt b/Documentation/filesystems/dax.txt
index 8fdb78f3c6c9..a5af22831087 100644
--- a/Documentation/filesystems/dax.txt
+++ b/Documentation/filesystems/dax.txt
@@ -84,19 +84,8 @@ Summary
described in 6) below.
6. When changing the S_DAX policy via toggling the persistent FS_XFLAG_DAX flag,
- the change in behaviour for existing regular files may not occur
- immediately. If the change must take effect immediately, the administrator
- needs to:
-
- a) stop the application so there are no active references to the data set
- the policy change will affect
-
- b) evict the data set from kernel caches so it will be re-instantiated when
- the application is restarted. This can be achieved by:
-
- i. drop-caches
- ii. a filesystem unmount and mount cycle
- iii. a system reboot
+ the change to existing regular file won't take effect until the file is closed
+ by all processes or all processes referencing the file are stopped.
Details
--
2.29.2
next reply other threads:[~2021-01-04 2:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 2:40 Hao Li [this message]
2021-01-04 16:36 ` Ira Weiny
2021-01-06 1:15 ` Li, Hao
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=20210104024040.5381-1-lihao2018.fnst@cn.fujitsu.com \
--to=lihao2018.fnst@cn.fujitsu.com \
--cc=alexander.deucher@amd.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=ira.weiny@intel.com \
--cc=lee.jones@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
/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
all inboxes | Powered by JetHome®