From: Tiago Sousa via pve-devel <pve-devel@lists.proxmox.com>
To: pve-devel@lists.proxmox.com
Cc: Tiago Sousa <joao.sousa@eurotux.com>
Subject: Re: [pve-devel] [RFC storage/qemu-server] Thin provisioning on LVM
Date: Fri, 25 Jul 2025 15:46:41 +0100 [thread overview]
Message-ID: <mailman.130.1753454806.367.pve-devel@lists.proxmox.com> (raw)
In-Reply-To: <mailman.104.1753437680.367.pve-devel@lists.proxmox.com>
[-- Attachment #1: Type: message/rfc822, Size: 4590 bytes --]
From: Tiago Sousa <joao.sousa@eurotux.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [RFC storage/qemu-server] Thin provisioning on LVM
Date: Fri, 25 Jul 2025 15:46:41 +0100
Message-ID: <6045867d-4fd6-4e29-b462-e37bfaba583c@eurotux.com>
Small correction, the write threshold should be applied to the file
node, since it's the one that will have the correct filesystem
wr_highest_offset.
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-07-25 14:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-25 10:00 Joao Sousa via pve-devel
2025-07-25 14:46 ` Tiago Sousa via pve-devel [this message]
2025-08-02 16:42 ` [pve-devel] [PATCH qemu-server 0/2] set write threshold logic Tiago Sousa via pve-devel
2025-08-04 9:14 ` Fiona Ebner
2025-08-11 20:34 ` Joao Sousa via pve-devel
[not found] ` <20250802164240.21751-1-joao.sousa@eurotux.com>
2025-08-02 16:42 ` [pve-devel] [PATCH qemu-server 1/2] blockdev: add set write threshold Tiago Sousa via pve-devel
2025-08-02 16:42 ` [pve-devel] [PATCH qemu-server 2/2] qmeventd: add block write threshold event handling Tiago Sousa via pve-devel
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=mailman.130.1753454806.367.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=joao.sousa@eurotux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.