From f815aa8909ee54eaf6166b345f5ad37e39379e95 Mon Sep 17 00:00:00 2001
From: Iustin Pop <iustin@google.com>
Date: Fri, 8 Jul 2011 15:32:23 +0200
Subject: [PATCH] htools: fix a doc bug in the hbal man page

Similar to the previous hspace fix.

Signed-off-by: Iustin Pop <iustin@google.com>
Reviewed-by: Michael Hanselmann <hansmi@google.com>
---
 man/hbal.rst | 14 ++++++++------
 1 file changed, 8 insertions(+), 6 deletions(-)

diff --git a/man/hbal.rst b/man/hbal.rst
index aea36024a..a032a89a0 100644
--- a/man/hbal.rst
+++ b/man/hbal.rst
@@ -440,12 +440,14 @@ The options that can be passed to the program are as follows:
   to automate the execution of the balancing.
 
 --max-cpu=*cpu-ratio*
-  The maximum virtual to physical cpu ratio, as a floating point
-  number between zero and one. For example, specifying *cpu-ratio* as
-  **2.5** means that, for a 4-cpu machine, a maximum of 10 virtual
-  cpus should be allowed to be in use for primary instances. A value
-  of one doesn't make sense though, as that means no disk space can be
-  used on it.
+  The maximum virtual to physical cpu ratio, as a floating point number
+  greater than or equal to one. For example, specifying *cpu-ratio* as
+  **2.5** means that, for a 4-cpu machine, a maximum of 10 virtual cpus
+  should be allowed to be in use for primary instances. A value of
+  exactly one means there will be no over-subscription of CPU (except
+  for the CPU time used by the node itself), and values below one do not
+  make sense, as that means other resources (e.g. disk) won't be fully
+  utilised due to CPU restrictions.
 
 --min-disk=*disk-ratio*
   The minimum amount of free disk space remaining, as a floating point
-- 
GitLab