From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH proxmox-resource-scheduling 2/2] pve ha: fix typo in comment
Date: Tue, 21 Mar 2023 13:33:43 +0100 [thread overview]
Message-ID: <20230321123345.128141-3-f.ebner@proxmox.com> (raw)
In-Reply-To: <20230321123345.128141-1-f.ebner@proxmox.com>
Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
---
src/pve_static.rs | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/pve_static.rs b/src/pve_static.rs
index 6663b70..814d44f 100644
--- a/src/pve_static.rs
+++ b/src/pve_static.rs
@@ -9,11 +9,11 @@ use crate::topsis;
pub struct StaticNodeUsage {
/// Hostname of the node.
pub name: String,
- /// CPU utilization. Can be more than `maxcpu` if overcommited.
+ /// CPU utilization. Can be more than `maxcpu` if overcommitted.
pub cpu: f64,
/// Total number of CPUs.
pub maxcpu: usize,
- /// Used memory in bytes. Can be more than `maxmem` if overcommited.
+ /// Used memory in bytes. Can be more than `maxmem` if overcommitted.
pub mem: usize,
/// Total memory in bytes.
pub maxmem: usize,
--
2.30.2
next prev parent reply other threads:[~2023-03-21 12:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 12:33 [pve-devel] [PATCH-SERIES proxmox-{resource-scheduling, perl-rs}] fix scoring issue with overcommitted node Fiona Ebner
2023-03-21 12:33 ` [pve-devel] [PATCH proxmox-resource-scheduling 1/2] pve ha: fix scoring issue when a node is overcommitted compared to others Fiona Ebner
2023-03-21 12:33 ` Fiona Ebner [this message]
2023-03-21 12:33 ` [pve-devel] [PATCH proxmox-perl-rs 1/2] pve: test: resource scheduling: use dedicated functions for tests Fiona Ebner
2023-03-21 12:33 ` [pve-devel] [PATCH proxmox-perl-rs 2/2] pve: test: resource scheduling: add test with overcommitted node Fiona Ebner
2023-03-21 14:25 ` [pve-devel] applied-series: [PATCH-SERIES proxmox-{resource-scheduling, perl-rs}] fix scoring issue " 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=20230321123345.128141-3-f.ebner@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