From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id B5A701FF187 for ; Mon, 20 Oct 2025 14:18:36 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 7FAE47138; Mon, 20 Oct 2025 14:18:24 +0200 (CEST) From: Markus Frank To: pve-devel@lists.proxmox.com Date: Mon, 20 Oct 2025 14:17:40 +0200 Message-ID: <20251020121807.280441-6-m.frank@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20251020121807.280441-1-m.frank@proxmox.com> References: <20251020121807.280441-1-m.frank@proxmox.com> MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1760962692708 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.000 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment KAM_SHORT 0.001 Use of a URL Shortener for very short URL SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pve-devel] [PATCH docs v1 5/11] virtiofs: add explanation for cache=metadata behavior X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" Adds a description of the `cache=metadata` mode and references the upstream patch that introduced it. Signed-off-by: Markus Frank --- qm.adoc | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/qm.adoc b/qm.adoc index 71df79e..664df5c 100644 --- a/qm.adoc +++ b/qm.adoc @@ -1326,7 +1326,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 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel