public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Daniel Kral <d.kral@proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>,
	"Laurențiu Leahu-Vlăducu" <l.leahu-vladucu@proxmox.com>
Subject: Re: [pve-devel] [PATCH manager v14 12/12] ui: add options to add virtio-fs to qemu config
Date: Wed, 2 Apr 2025 16:06:53 +0200	[thread overview]
Message-ID: <e9bf4ee9-ae45-4505-b187-e762697b907d@proxmox.com> (raw)
In-Reply-To: <e5e109c6-0703-4b52-9958-f0037cf4ddfc@proxmox.com>

On 4/2/25 12:36, Laurențiu Leahu-Vlăducu wrote:
> Is it a good idea to use cache=auto by default? I know that "cache=auto" 
> is the upstream default, but I was wondering whether it's not safer to 
> use "never" by default in PVE to minimize the amount of potential 
> issues. Feel free to contradict me, though ;)
> 
> By searching the internet I found some reports regarding cache=auto, 
> e.g. https://discuss.linuxcontainers.org/t/current-state-of-virtiofs- 
> under-virtual-machines/19166

Good point!

Additionally, there's a 'metadata' option upstream which seems like a 
compromise and might be another good option to add as soon as it's 
available from the Debian repositories or build them ourselves.

On 4/2/25 12:36, Laurențiu Leahu-Vlăducu wrote:
> I think some of these options should be marked as advanced, as they 
> won't be needed in most cases (feel free to contradict me, though).
> 
> While it's not always immediately clear what some of these options do, I 
> think it's hard to summarize the functionality in a short tooltip, so 
> linking to the docs (as you already do) is fine to me.
> 
> What is still unclear to me is what some caching combinations do, e.g. 
> the user can set Cache to Never, but can also enable "Writeback cache". 
> I know this has to do with QEMU and you simply exposed the GUI for 
> setting the advanced options, but I was just wondering whether it 
> wouldn't be possible to expose these options to our users in a way that 
> the difference between the modes is clearer, e.g. "Read cache" and 
> "Writeback cache". Feel free to use some entirely different naming, 
> though ;)

I also agree putting it at least in the "Advanced" section, but I'd not 
change the names too much from what virtiofs is exposing, but rather 
make it clear in the documentation or in some other form what the 
difference between both are.

The cache policy set by `cache={auto,always,never}` sets O_DIRECT for 
files with `cache=never` and FUSE's `KEEP_CACHE` for files with 
`cache=always` [0].

Some details for the writeback option are documented here [1].

[0] 
https://gitlab.com/virtio-fs/virtiofsd/-/blob/main/src/passthrough/mod.rs#L953
[1] 
https://gitlab.com/virtio-fs/virtiofsd/-/blob/main/src/passthrough/mod.rs#L231


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

  reply	other threads:[~2025-04-02 14:07 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-04 11:57 [pve-devel] [PATCH cluster/guest-common/docs/qemu-server/manager v14 0/12] virtiofs Markus Frank
2025-03-04 11:57 ` [pve-devel] [PATCH cluster v14 1/12] add mapping/dir.cfg for resource mapping Markus Frank
2025-03-04 11:57 ` [pve-devel] [PATCH guest-common v14 2/12] add dir mapping section config Markus Frank
2025-04-02 13:14   ` Fabian Grünbichler
2025-04-02 15:20     ` Markus Frank
2025-04-02 13:41   ` Daniel Kral
2025-03-04 11:57 ` [pve-devel] [PATCH docs v14 3/12] add doc section for the shared filesystem virtio-fs Markus Frank
2025-04-02 10:36   ` Laurențiu Leahu-Vlăducu
2025-04-02 13:13   ` Fabian Grünbichler
2025-04-02 13:44   ` Daniel Kral
2025-03-04 11:57 ` [pve-devel] [PATCH qemu-server v14 4/12] control: add virtiofsd as runtime dependency for qemu-server Markus Frank
2025-03-04 11:57 ` [pve-devel] [PATCH qemu-server v14 5/12] fix #1027: virtio-fs support Markus Frank
2025-04-02 13:13   ` Fabian Grünbichler
2025-03-04 11:57 ` [pve-devel] [PATCH qemu-server v14 6/12] migration: check_local_resources for virtiofs Markus Frank
2025-04-02 13:13   ` Fabian Grünbichler
2025-03-04 11:57 ` [pve-devel] [PATCH qemu-server v14 7/12] disable snapshot (with RAM) and hibernate with virtio-fs devices Markus Frank
2025-03-04 11:57 ` [pve-devel] [PATCH manager v14 08/12] api: add resource map api endpoints for directories Markus Frank
2025-03-04 11:58 ` [pve-devel] [PATCH manager v14 09/12] ui: add edit window for dir mappings Markus Frank
2025-03-04 11:58 ` [pve-devel] [PATCH manager v14 10/12] ui: add resource mapping view for directories Markus Frank
2025-04-02 10:36   ` Laurențiu Leahu-Vlăducu
2025-04-02 13:42   ` Daniel Kral
2025-03-04 11:58 ` [pve-devel] [PATCH manager v14 11/12] ui: form: add selector for directory mappings Markus Frank
2025-03-04 11:58 ` [pve-devel] [PATCH manager v14 12/12] ui: add options to add virtio-fs to qemu config Markus Frank
2025-04-02 10:36   ` Laurențiu Leahu-Vlăducu
2025-04-02 14:06     ` Daniel Kral [this message]
2025-04-02 13:42   ` Daniel Kral
2025-03-18  9:14 ` [pve-devel] [PATCH cluster/guest-common/docs/qemu-server/manager v14 0/12] virtiofs Markus Frank
2025-04-02 10:36 ` Laurențiu Leahu-Vlăducu
2025-04-02 13:17 ` Fabian Grünbichler
2025-04-02 13:45 ` Daniel Kral

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=e9bf4ee9-ae45-4505-b187-e762697b907d@proxmox.com \
    --to=d.kral@proxmox.com \
    --cc=l.leahu-vladucu@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal