From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pbs-devel@lists.proxmox.com, Nicolas Frey <n.frey@proxmox.com>
Subject: [pbs-devel] applied: [PATCH proxmox{, -backup} v2 0/7] tuning: verify: add verify job thread options
Date: Mon, 24 Nov 2025 15:16:20 +0100 [thread overview]
Message-ID: <176399375130.1954288.4880700490503555409.b4-ty@proxmox.com> (raw)
In-Reply-To: <20251124110427.194887-1-n.frey@proxmox.com>
On Mon, 24 Nov 2025 12:04:20 +0100, Nicolas Frey wrote:
> this patch series aims to expose configuration of the number of threads
> to use for reading and verifying of verify jobs through the datastore's
> tuning options.
>
> It expands on the series I sent last week [0], where @Thomas
> suggested making this configurable through the tuning options too.
> @Chris suggested adding a dedicated worker thread settings to the
> datastore instead, which is an approach I don't have a problem with,
> but I'd want some more opinions on.
>
> [...]
Applied, thanks!
[1/1] pbs-api-types: add default-verification-{workers, readers} to tuning options
commit: 9be1e40f56224efd385d851ad1ac74070a631307
[1/6] datastore: add new thread settings to tuning options
commit: 568e11a4913629f934e95e5b1f38159a2d506581
[2/6] verify: use tuning options' thread settings for {verify, read}-threads
commit: 2165ea5b2023312c67728ae0d2d223ce758d6971
[3/6] ui: tuning: make default-verification-{workers, readers} configurable
commit: ea62a3bc7572253427faec38911e02796d0acc0b
[4/6] ui: tuning: render verification threads in tuning options
commit: 23262e2bfa182bc80437665ad20865f02a5d8d94
[5/6] ui: verify: fetch default {read, verify} thread values from tuning options
commit: 88d419d2cee3e91d5b1a55f2d163ded1b0591db6
[6/6] docs: tuning: document default-verification-{workers, readers}
commit: a3302af5d10a7adc3fa80e228f3715672583e80e
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
prev parent reply other threads:[~2025-11-24 14:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-24 11:04 [pbs-devel] " Nicolas Frey
2025-11-24 11:04 ` [pbs-devel] [PATCH proxmox v2 1/1] pbs-api-types: add default-verification-{workers, readers} to tuning options Nicolas Frey
2025-11-24 11:04 ` [pbs-devel] [PATCH proxmox-backup v2 1/6] datastore: add new thread settings " Nicolas Frey
2025-11-24 11:04 ` [pbs-devel] [PATCH proxmox-backup v2 2/6] verify: use tuning options' thread settings for {verify, read}-threads Nicolas Frey
2025-11-24 11:04 ` [pbs-devel] [PATCH proxmox-backup v2 3/6] ui: tuning: make default-verification-{workers, readers} configurable Nicolas Frey
2025-11-24 11:04 ` [pbs-devel] [PATCH proxmox-backup v2 4/6] ui: tuning: render verification threads in tuning options Nicolas Frey
2025-11-24 11:04 ` [pbs-devel] [PATCH proxmox-backup v2 5/6] ui: verify: fetch default {read, verify} thread values from " Nicolas Frey
2025-11-24 11:04 ` [pbs-devel] [PATCH proxmox-backup v2 6/6] docs: tuning: document default-verification-{workers, readers} Nicolas Frey
2025-11-24 12:41 ` [pbs-devel] [PATCH proxmox{, -backup} v2 0/7] tuning: verify: add verify job thread options Christian Ebner
2025-11-24 14:16 ` 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=176399375130.1954288.4880700490503555409.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=n.frey@proxmox.com \
--cc=pbs-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