From: Alwin Antreich via pve-devel <pve-devel@lists.proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>
Cc: Alwin Antreich <alwin@antreich.com>
Subject: Re: [pve-devel] [PATCH docs 1/2] pve-storage-lvm: add saferemove_throughput limit
Date: Mon, 10 Nov 2025 10:05:27 +0000 [thread overview]
Message-ID: <mailman.819.1762769137.362.pve-devel@lists.proxmox.com> (raw)
In-Reply-To: <mailman.372.1761744478.362.pve-devel@lists.proxmox.com>
[-- Attachment #1: Type: message/rfc822, Size: 4343 bytes --]
From: "Alwin Antreich" <alwin@antreich.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH docs 1/2] pve-storage-lvm: add saferemove_throughput limit
Date: Mon, 10 Nov 2025 10:05:27 +0000
Message-ID: <5ecba160c509db7ed3bbac8b62cd1f9b8892824b@antreich.com>
Hi,
Is mentioning the limit like this ok or is there a better way?
Cheers,
Alwin
October 29, 2025 at 2:27 PM, "Alwin Antreich via pve-devel" <pve-devel@lists.proxmox.com mailto:pve-devel@lists.proxmox.com?to=%22Alwin%20Antreich%20via%20pve-devel%22%20%3Cpve-devel%40lists.proxmox.com%3E > wrote:
>
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com mailto:pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>
[-- 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-11-10 10:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 13:27 Alwin Antreich via pve-devel
2025-11-10 10:05 ` Alwin Antreich via pve-devel [this message]
2025-11-11 15:32 ` [pve-devel] applied: " Fiona Ebner
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.819.1762769137.362.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=alwin@antreich.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