From: Markus Frank <m.frank@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH docs v3 5/11] virtiofs: add explanation for cache=metadata behavior
Date: Mon, 27 Apr 2026 14:16:54 +0200 [thread overview]
Message-ID: <20260427121746.270544-6-m.frank@proxmox.com> (raw)
In-Reply-To: <20260427121746.270544-1-m.frank@proxmox.com>
Adds a description of the `cache=metadata` mode and references the
upstream patch that introduced it.
Signed-off-by: Markus Frank <m.frank@proxmox.com>
---
v3: no changes
qm.adoc | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/qm.adoc b/qm.adoc
index e6b7918..46edeb3 100644
--- a/qm.adoc
+++ b/qm.adoc
@@ -1378,7 +1378,9 @@ has been configured in the resource mapping. Additionally, you can set the
`cache` option to either `always`, `never`, `metadata`, or `auto` (default:
`auto`), depending on your requirements. How the different caching modes behave
can be read https://lwn.net/Articles/774495/[here under the "Caching Modes"
-section].
+section]. The https://gitlab.com/virtio-fs/virtiofsd/-/commit/598ca8e[`metadata`]
+policy is similar to `never`, but it allows guests to cache filesystem metadata,
+such as dcache and attr.
The `virtiofsd` supports ACL and xattr passthrough (can be enabled with the
`expose-acl` and `expose-xattr` options), allowing the guest to access ACLs and
--
2.47.3
next prev parent reply other threads:[~2026-04-27 12:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 12:16 [PATCH guest-common/qemu-server/docs/manager v3 0/11] Virtiofs improvements Markus Frank
2026-04-27 12:16 ` [PATCH guest-common v3 1/11] mapping: dir: add 'live-migration-method' parameter Markus Frank
2026-04-27 12:16 ` [PATCH qemu-server v3 2/11] fix #6370: virtiofs: add support for thread-pool-size option Markus Frank
2026-04-27 12:16 ` [PATCH qemu-server v3 3/11] virtiofs: add readonly option Markus Frank
2026-04-27 12:16 ` [PATCH qemu-server v3 4/11] virtiofs: add live migration support Markus Frank
2026-04-27 12:16 ` Markus Frank [this message]
2026-04-27 12:16 ` [PATCH docs v3 6/11] virtiofs: add table for optional parameters Markus Frank
2026-04-27 12:16 ` [PATCH docs v3 7/11] virtiofs: add description for thread-pool-size and readonly Markus Frank
2026-04-27 12:16 ` [PATCH docs v3 8/11] virtiofs: add documentation for live migration Markus Frank
2026-04-27 12:16 ` [PATCH manager v3 09/11] fix #6370: ui: virtiofs edit: add support for thread-pool-size option Markus Frank
2026-04-27 12:16 ` [PATCH manager v3 10/11] virtiofs edit: add support for readonly option Markus Frank
2026-04-27 12:17 ` [PATCH manager v3 11/11] directory mapping: add live-migration-method option for virtiofs Markus Frank
2026-04-27 15:18 ` [PATCH guest-common/qemu-server/docs/manager v3 0/11] Virtiofs improvements Filip Schauer
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=20260427121746.270544-6-m.frank@proxmox.com \
--to=m.frank@proxmox.com \
--cc=pve-devel@lists.proxmox.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