From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pbs-devel@lists.proxmox.com, Christian Ebner <c.ebner@proxmox.com>
Subject: [pbs-devel] applied: [PATCH proxmox v3 1/5] rate-limiter: add crate for traffic rate limiter implementations
Date: Fri, 21 Nov 2025 20:04:10 +0100 [thread overview]
Message-ID: <176375185663.2058166.3077398897031086089.b4-ty@proxmox.com> (raw)
In-Reply-To: <20251112115353.277514-2-c.ebner@proxmox.com>
On Wed, 12 Nov 2025 12:53:45 +0100, Christian Ebner wrote:
> Factors out the traffic rate limiter implementations currently tied
> to the proxmox-backup and proxmox-http crates to make them
> independent and easily reusable, e.g. for the s3-client
> implementation.
>
> The shared rate limiter implementation from PBS relies on mmapping
> for state sharing, the file exposed having a predefined magic number.
> In order to be backwards compatible, leave the magic number as is and
> only adapt the constant name to be more generic, although the string
> the magic number is derived from is PBS specific.
>
> [...]
Applied, thanks!
[1/5] rate-limiter: add crate for traffic rate limiter implementations
commit: 7612fe31b021b241aab7ae2beb999ea10d2e0bcb
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next prev parent reply other threads:[~2025-11-21 19:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 11:53 [pbs-devel] [PATCH proxmox{, -backup} v3 0/9] shared rate limiter for s3 client instances Christian Ebner
2025-11-12 11:53 ` [pbs-devel] [PATCH proxmox v3 1/5] rate-limiter: add crate for traffic rate limiter implementations Christian Ebner
2025-11-21 19:04 ` Thomas Lamprecht [this message]
2025-11-12 11:53 ` [pbs-devel] [PATCH proxmox v3 2/5] rate-limiter: avoid division by zero in traffic updater Christian Ebner
2025-11-21 19:04 ` [pbs-devel] applied: " Thomas Lamprecht
2025-11-12 11:53 ` [pbs-devel] [PATCH proxmox v3 3/5] http: drop factored out rate limiter implementation Christian Ebner
2025-11-21 19:04 ` [pbs-devel] applied: " Thomas Lamprecht
2025-11-12 11:53 ` [pbs-devel] [PATCH proxmox v3 4/5] rest-server: optionally depend on factored out shared rate limiter Christian Ebner
2025-11-21 19:04 ` [pbs-devel] applied: " Thomas Lamprecht
2025-11-12 11:53 ` [pbs-devel] [PATCH proxmox v3 5/5] s3-client: add shared rate limiter via https connector Christian Ebner
2025-11-21 19:04 ` [pbs-devel] applied: " Thomas Lamprecht
2025-11-12 11:53 ` [pbs-devel] [PATCH proxmox-backup v3 1/4] traffic control: use factored out shared rate limiter Christian Ebner
2025-11-21 19:04 ` [pbs-devel] applied: " Thomas Lamprecht
2025-11-12 11:53 ` [pbs-devel] [PATCH proxmox-backup v3 2/4] api: config: update s3 endpoint rate limits in config Christian Ebner
2025-11-21 19:04 ` [pbs-devel] applied: " Thomas Lamprecht
2025-11-12 11:53 ` [pbs-devel] [PATCH proxmox-backup v3 3/4] datastore: s3: set rate limiter options for s3 client Christian Ebner
2025-11-21 19:04 ` [pbs-devel] applied: " Thomas Lamprecht
2025-11-12 11:53 ` [pbs-devel] [PATCH proxmox-backup v3 4/4] ui: expose rate and burst limits for s3 endpoints Christian Ebner
2025-11-21 19:04 ` [pbs-devel] applied: " Thomas Lamprecht
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=176375185663.2058166.3077398897031086089.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=c.ebner@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.