From: Christian Schoenebeck <linux_oss@crudebyte.com>
To: v9fs-developer@lists.sourceforge.net,
Eric Van Hensbergen <ericvh@kernel.org>
Cc: asmadeus@codewreck.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fs/9p: Add new options to Documentation
Date: Mon, 27 Mar 2023 17:38:41 +0200 [thread overview]
Message-ID: <3443961.DhAEVoPbTG@silver> (raw)
In-Reply-To: <ZCEIEKC0s/MFReT0@7e9e31583646>
On Monday, March 27, 2023 5:05:52 AM CEST Eric Van Hensbergen wrote:
> Need to update the documentation for new mount flags
> and cache modes.
>
> Signed-off-by: Eric Van Hensbergen <ericvh@kernel.org>
> ---
> Documentation/filesystems/9p.rst | 29 ++++++++++++++++-------------
> 1 file changed, 16 insertions(+), 13 deletions(-)
>
> diff --git a/Documentation/filesystems/9p.rst b/Documentation/filesystems/9p.rst
> index 0e800b8f73cc..6d257854a02a 100644
> --- a/Documentation/filesystems/9p.rst
> +++ b/Documentation/filesystems/9p.rst
> @@ -78,19 +78,18 @@ Options
> offering several exported file systems.
>
> cache=mode specifies a caching policy. By default, no caches are used.
> -
> - none
> - default no cache policy, metadata and data
> - alike are synchronous.
> - loose
> - no attempts are made at consistency,
> - intended for exclusive, read-only mounts
> - fscache
> - use FS-Cache for a persistent, read-only
> - cache backend.
> - mmap
> - minimal cache that is only used for read-write
> - mmap. Northing else is cached, like cache=none
> + Modes are progressive and inclusive. For example, specifying fscache
> + will use loose caches, writeback, and readahead. Due to their
> + inclusive nature, only one cache mode can be specified per mount.
I would highly recommend to rather specify below for each option "this option
implies writeback, readahead ..." etc., as it is not obvious otherwise which
option would exactly imply what. It is worth those extra few lines IMO to
avoid confusion.
> +
> + ========= =============================================
> + none no cache of file or metadata
> + readahead readahead caching of files
> + writeback delayed writeback of files
> + mmap support mmap operations read/write with cache
> + loose meta-data and file cache with no coherency
> + fscache use FS-Cache for a persistent cache backend
> + ========= =============================================
>
> debug=n specifies debug level. The debug level is a bitmask.
>
> @@ -137,6 +136,10 @@ Options
> This can be used to share devices/named pipes/sockets between
> hosts. This functionality will be expanded in later versions.
>
> + directio bypass page cache on all read/write operations
> +
> + ignoreqv ignore qid.version==0 as a marker to ignore cache
> +
> noxattr do not offer xattr functions on this mount.
>
> access there are four access modes.
>
next prev parent reply other threads:[~2023-03-27 16:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 3:05 [PATCH] fs/9p: Add new options to Documentation Eric Van Hensbergen
2023-03-27 15:38 ` Christian Schoenebeck [this message]
2023-03-28 15:51 ` Eric Van Hensbergen
2023-04-02 14:07 ` Christian Schoenebeck
2023-04-02 18:22 ` asmadeus
2023-04-02 18:43 ` Eric Van Hensbergen
2023-04-04 18:26 ` Jeff Layton
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=3443961.DhAEVoPbTG@silver \
--to=linux_oss@crudebyte.com \
--cc=asmadeus@codewreck.org \
--cc=ericvh@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=v9fs-developer@lists.sourceforge.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;
as well as URLs for NNTP newsgroup(s).