all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] applied: [PATCH v5 pve-storage 1/2] lvmplugin: use blkdiscard when supported instead cstream to saferemove drive
Date: Mon, 27 Oct 2025 16:47:48 +0100	[thread overview]
Message-ID: <176157999946.101495.597024781817448800.b4-ty@proxmox.com> (raw)
In-Reply-To: <mailman.253.1761222252.362.pve-devel@lists.proxmox.com>

On Thu, 23 Oct 2025 14:23:30 +0200, Alexandre Derumier via pve-devel wrote:
> Current cstream implementation is pretty slow, even without throttling.
> 
> use blkdiscard --zeroout instead when storage support it,
> which is a few magnitudes faster.
> 
> Another benefit is that blkdiscard is skipping already zeroed block, so for empty
> temp images like snapshot, is pretty fast.
> 
> [...]

Applied both patches, with some minor language and style fixups
squashed in, thanks!

[1/2] lvmplugin: use blkdiscard when supported instead cstream to saferemove drive
      commit: 728d8f39925d2c694ee49c79d65c2156f2553a9a
[2/2] fix #6941: lvmplugin: fix volume activation of raw disk before secure delete
      commit: d5995ffbf73235840fdbd281aeb5034f669a410f


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


  reply	other threads:[~2025-10-27 15:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251023122331.477027-1-alexandre.derumier@groupe-cyllene.com>
2025-10-23 12:23 ` [pve-devel] " Alexandre Derumier via pve-devel
2025-10-27 15:47   ` Fiona Ebner [this message]
2025-10-23 12:23 ` [pve-devel] [PATCH v5 pve-storage 2/2] fix #6941 : lvmplugin : fix volume activation of raw disk before secure delete Alexandre Derumier 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=176157999946.101495.597024781817448800.b4-ty@proxmox.com \
    --to=f.ebner@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 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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal