From: Cole Robinson <crobinso@redhat.com>
Date: Mon, 22 Feb 2010 20:52:14 +0000 (-0500)
Subject: docs: storage: Document capacity/alloc 'unit'
X-Git-Tag: v0.7.7~101
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=3a6555b3457477011df70366f3f1213025ef09e0;p=thirdparty%2Flibvirt.git

docs: storage: Document capacity/alloc 'unit'
---

diff --git a/docs/formatstorage.html.in b/docs/formatstorage.html.in
index 5c41c39821..6dbe0cab8e 100644
--- a/docs/formatstorage.html.in
+++ b/docs/formatstorage.html.in
@@ -215,10 +215,18 @@
         allocated at time of creation. If set to a value smaller than the
         capacity, the pool has the <strong>option</strong> of deciding
         to sparsely allocate a volume. It does not have to honour requests
-        for sparse allocation though. <span class="since">Since 0.4.1</span></dd>
+        for sparse allocation though.<br/>
+        <br/>
+        By default this is specified in bytes, but an optional
+        <code>unit</code> can be specified to adjust the passed value.
+        Values can be: 'K' (kilobytes), 'M' (megabytes), 'G' (gigabytes),
+        'T' (terabytes), 'P' (petabytes), or 'E' (exabytes).
+        <span class="since">Since 0.4.1</span></dd>
       <dt><code>capacity</code></dt>
       <dd>Providing the logical capacity for the volume. This value is
-        in bytes. This is compulsory when creating a volume.
+        in bytes by default, but a <code>unit</code> attribute can be
+        specified with the same semantics as for <code>allocation</code>
+        This is compulsory when creating a volume.
         <span class="since">Since 0.4.1</span></dd>
       <dt><code>source</code></dt>
       <dd>Provides information about the underlying storage allocation