From: Hannes Laimer <h.laimer@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: Re: [pbs-devel] [RFC proxmox{, -backup} 0/6] add support for configuring max
Date: Thu, 6 Nov 2025 10:41:43 +0100 [thread overview]
Message-ID: <37a5160b-a954-4045-9ad8-a8116aa5aead@proxmox.com> (raw)
In-Reply-To: <20250904143735.125857-1-h.laimer@proxmox.com>
ping
On 9/4/25 16:37, Hannes Laimer wrote:
> This uses POSIX semaphores to control how many backups run at any given
> time. Semaphores seemed like a fitting choice given the problem, so I
> added a basic wrapper for named ones to proxmox-sys. Also, the changes
> needed to add concurrency limits in PBS were minimal.
>
> A few questions I still have and would be great to get some feedback on,
> - do we want to use semaphores like proposed here? Are there any good
> reasons not to?
> - should we include things like verify/gc/prune? Would an extra sem for
> reading make sense(so separate limits for r and w, idk if there's a
> use-case)?
>
> Nothing UI-wise is included, and for changes to apply the proxy has to
> be restarted. Not sure if restarting the proxy is "ok-ish" ux wise, I
> guess not :P But changing it involves re-creating the semaphore, which
> is fine, just that there won't exist one for a really short time...
>
>
> proxmox:
>
> Hannes Laimer (2):
> sys: add wrapper for POSIX semaphores
> pbs-api-types: add concurrency_limit to DataStoreConfig
>
> pbs-api-types/src/datastore.rs | 5 +
> proxmox-sys/Cargo.toml | 1 +
> proxmox-sys/src/lib.rs | 2 +
> proxmox-sys/src/semaphore.rs | 164 +++++++++++++++++++++++++++++++++
> 4 files changed, 172 insertions(+)
> create mode 100644 proxmox-sys/src/semaphore.rs
>
>
> proxmox-backup:
>
> Hannes Laimer (4):
> api: config: update/delete concurrency_limit on datastore
> Cargo.toml: add 'semaphore' feature to proxmox-sys dep
> bin: proxy: initialize concurrency semaphores for datastores
> api: backup: wait for semaphore if one exists
>
> Cargo.toml | 2 +-
> src/api2/backup/mod.rs | 24 ++++++++++++++++++++++--
> src/api2/config/datastore.rs | 9 +++++++++
> src/bin/proxmox-backup-proxy.rs | 11 +++++++++++
> 4 files changed, 43 insertions(+), 3 deletions(-)
>
>
> Summary over all repositories:
> 8 files changed, 215 insertions(+), 3 deletions(-)
>
_______________________________________________
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-06 9:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 14:37 Hannes Laimer
2025-09-04 14:37 ` [pbs-devel] [PATCH proxmox 1/2] sys: add wrapper for POSIX semaphores Hannes Laimer
2025-09-04 14:37 ` [pbs-devel] [PATCH proxmox 2/2] pbs-api-types: add concurrency_limit to DataStoreConfig Hannes Laimer
2025-09-04 14:37 ` [pbs-devel] [PATCH proxmox-backup 1/4] api: config: update/delete concurrency_limit on datastore Hannes Laimer
2025-09-04 14:37 ` [pbs-devel] [PATCH proxmox-backup 2/4] Cargo.toml: add 'semaphore' feature to proxmox-sys dep Hannes Laimer
2025-09-04 14:37 ` [pbs-devel] [PATCH proxmox-backup 3/4] bin: proxy: initialize concurrency semaphores for datastores Hannes Laimer
2025-09-04 14:37 ` [pbs-devel] [PATCH proxmox-backup 4/4] api: backup: wait for semaphore if one exists Hannes Laimer
2025-11-06 9:41 ` Hannes Laimer [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=37a5160b-a954-4045-9ad8-a8116aa5aead@proxmox.com \
--to=h.laimer@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 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.