From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Stoiko Ivanov <s.ivanov@proxmox.com>
Subject: Re: [pve-devel] [RFC pve-kernel] add disable_write_zeroes quirk for Crucial T700 and T705
Date: Fri, 21 Mar 2025 12:44:31 +0100 [thread overview]
Message-ID: <ef8823e6-1575-4e40-8432-6beb65267f16@proxmox.com> (raw)
In-Reply-To: <20250319203338.1599401-1-s.ivanov@proxmox.com>
Am 19.03.25 um 21:33 schrieb Stoiko Ivanov:
> The patch seems to indeed improve the performance of BLKZEROOUT and
> other operations that use write_zeroes for both drives.
>
> Tested with LVM-thick LVs on both drives, as LVM seems to pass-through the
> write_zeroes_max_bytes property (going by the output of:
> /sys/block/nvmeXn1/queue/write_zeroes_max_bytes).
>
> however as the T705 drives in our pool are all in use the test there was
> limited to a rather small LV of 350M (still the change was from 5
> seconds to 0.5 seconds).
>
> Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
> ---
> sending as RFC, as I'm not certain if that approach makes sense in
> general, or if maybe other drives are also affected (or if some other
> sizes of T705, T700 are not affected).
not sure how much anybody here can comment on that, maybe send it upstream
and CC a relevant maintainer, ideally one working for crucial/micron.
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-03-21 11:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 20:33 Stoiko Ivanov
2025-03-21 11:44 ` Thomas Lamprecht [this message]
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=ef8823e6-1575-4e40-8432-6beb65267f16@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.ivanov@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