From: Jingbo Xu <jefflexu@linux.alibaba.com>
To: xiang@kernel.org, chao@kernel.org, linux-erofs@lists.ozlabs.org
Cc: huyue2@coolpad.com
Subject: [PATCH 1/2] erofs: add documentation for 'domain_id' mount option
Date: Wed, 11 Jan 2023 16:15:46 +0800 [thread overview]
Message-ID: <20230111081547.126322-2-jefflexu@linux.alibaba.com> (raw)
In-Reply-To: <20230111081547.126322-1-jefflexu@linux.alibaba.com>
The share domain feature for fscache mode has been merged, and let's add
documentation for 'domain_id' mount option.
Signed-off-by: Jingbo Xu <jefflexu@linux.alibaba.com>
---
Documentation/filesystems/erofs.rst | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/filesystems/erofs.rst b/Documentation/filesystems/erofs.rst
index 067fd1670b1f..958cad2c4997 100644
--- a/Documentation/filesystems/erofs.rst
+++ b/Documentation/filesystems/erofs.rst
@@ -120,6 +120,9 @@ dax={always,never} Use direct access (no page cache). See
dax A legacy option which is an alias for ``dax=always``.
device=%s Specify a path to an extra device to be used together.
fsid=%s Specify a filesystem image ID for Fscache back-end.
+domain_id=%s Specify a domain ID for Fscache back-end. The blob
+ images are shared among filesystem instances in the same
+ domain.
=================== =========================================================
Sysfs Entries
--
2.19.1.6.gb485710b
next prev parent reply other threads:[~2023-01-11 8:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 8:15 [PATCH 0/2] erofs: misc cleanups for fscache mode Jingbo Xu
2023-01-11 8:15 ` Jingbo Xu [this message]
2023-01-11 8:38 ` [External] [PATCH 1/2] erofs: add documentation for 'domain_id' mount option Jia Zhu
2023-01-11 8:46 ` Gao Xiang
2023-01-11 8:15 ` [PATCH 2/2] erofs: clean up parsing of fscache related options Jingbo Xu
2023-01-11 9:09 ` [External] " Jia Zhu
2023-01-12 5:31 ` Gao Xiang
2023-01-12 5:56 ` Yue Hu
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=20230111081547.126322-2-jefflexu@linux.alibaba.com \
--to=jefflexu@linux.alibaba.com \
--cc=chao@kernel.org \
--cc=huyue2@coolpad.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=xiang@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