From: Jingbo Xu <jefflexu@linux.alibaba.com>
To: xiang@kernel.org, chao@kernel.org, linux-erofs@lists.ozlabs.org
Cc: huyue2@coolpad.com, linux-doc@vger.kernel.org
Subject: Re: [PATCH v2 1/2] erofs: add documentation for 'domain_id' mount option
Date: Thu, 12 Jan 2023 14:55:59 +0800 [thread overview]
Message-ID: <d2c6aca7-b2ed-1df6-c97a-246256fd0e18@linux.alibaba.com> (raw)
In-Reply-To: <20230112065431.124926-2-jefflexu@linux.alibaba.com>
cc: linux-doc@vger.kernel.org
On 1/12/23 2:54 PM, Jingbo Xu wrote:
> Since the EROFS share domain feature for fscache mode has been available
> since Linux v6.1, let's add documentation for 'domain_id' mount option.
>
> Cc: linux-doc@vger.kernel.org
> Reviewed-by: Jia Zhu <zhujia.zj@bytedance.com>
> Signed-off-by: Jingbo Xu <jefflexu@linux.alibaba.com>
> ---
> Documentation/filesystems/erofs.rst | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/Documentation/filesystems/erofs.rst b/Documentation/filesystems/erofs.rst
> index 067fd1670b1f..a43aacf1494e 100644
> --- a/Documentation/filesystems/erofs.rst
> +++ b/Documentation/filesystems/erofs.rst
> @@ -120,6 +120,8 @@ 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 in fscache mode so that different images
> + with the same blobs under a given domain ID can share storage.
> =================== =========================================================
>
> Sysfs Entries
--
Thanks,
Jingbo
next prev parent reply other threads:[~2023-01-12 6:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 6:54 [PATCH v2 0/2] erofs: misc cleanups for fscache mode Jingbo Xu
2023-01-12 6:54 ` [PATCH v2 1/2] erofs: add documentation for 'domain_id' mount option Jingbo Xu
2023-01-12 6:55 ` Jingbo Xu [this message]
2023-01-12 9:05 ` Gao Xiang
2023-01-16 13:33 ` Chao Yu
2023-01-12 6:54 ` [PATCH v2 2/2] erofs: clean up parsing of fscache related options Jingbo Xu
2023-01-16 13:34 ` Chao Yu
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=d2c6aca7-b2ed-1df6-c97a-246256fd0e18@linux.alibaba.com \
--to=jefflexu@linux.alibaba.com \
--cc=chao@kernel.org \
--cc=huyue2@coolpad.com \
--cc=linux-doc@vger.kernel.org \
--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