Changeset 29194 in vbox for trunk/src/VBox

Timestamp:

May 7, 2010 10:07:01 AM (15 years ago)

Author:

vboxsync

Message:

Main: fix newio docs again

File:

• trunk/src/VBox/Main/idl/VirtualBox.xidl (modified) (2 diffs)

trunk/src/VBox/Main/idl/VirtualBox.xidl

@@ -1096 +1096 @@
 
   <enum
+       name="IoBackendType"
+       uuid="2a7e16d1-4e6b-4d5d-b0c9-b9bbe6c5b2ad"
+       >
+    <desc>
+      Type of I/O backend used for the image files in a virtual machine.
+    </desc>
+    <const name="Buffered" value="1">
+      <desc>Image files will use the host cache if possible.
+        The storage controller emulation will use a dedicated I/O thread, enable the host I/O cache and
+        use synchronous file APIs on the host.
+        This type does not work with the Async I/O manager on Linux hosts.
+        This was the only option in the API before VirtualBox 3.2 and is still the default for IDE controllers.</desc>
+    </const>
+    <const name="Unbuffered" value="2">
+      <desc>Image files will not use the host cache.
+        The storage controller emulation will use asynchronous I/O APIs on the host. This makes it possible
+        to turn off the host I/O caches because it can handle unaligned access to the file.
+        This should be used on OS X and Linux hosts if a high I/O load is expected
+        or many virtual machines are running to prevent I/O cache related hangs.
+        This is new with the API of version 3.2 and is now the default for non-IDE storage controllers.</desc>
+    </const>
+  </enum>
+
+  <enum
    name="IoMgrType"
    uuid="35567419-4d2a-4256-a74e-efcae33493a2"
    >
      <desc>
-       Type of the I/O manager used for the image files in a virtual machine.
+       Type of the I/O manager used for the image files in a virtual machine if the backend is
+       set to the "Unbuffered" type.
      </desc>
      <const name="Simple" value="1">
@@ -1111 +1136 @@
      </const>
    </enum>
-
-  <enum
-   name="IoBackendType"
-   uuid="2a7e16d1-4e6b-4d5d-b0c9-b9bbe6c5b2ad"
-   >
-     <desc>
-       Type of I/O backend used for the image files in a virtual machine.
-     </desc>
-     <const name="Buffered" value="1">
-       <desc>Image files will use the host cache if possible.
-       The storage controller emulation will use a dedicated I/O thread, enable the host I/O cache and
-       use synchronous file APIs on the host.
-       This type does not work with the Async I/O manager on Linux hosts.
-       This was the only option before VirtualBox 3.2 and is still the default for IDE controllers.</desc>
-     </const>
-     <const name="Unbuffered" value="2">
-       <desc>Image files will not use the host cache.
-       The storage controller emulation will use asynchronous I/O APIs on the host. This makes it possible
-       to turn off the host I/O caches because it can handle unaligned access to the file.
-       This should be used on OS X and Linux hosts if a high I/O load is expected
-       or many virtual machines are running to prevent I/O cache related hangs.
-       This is new with version 3.2 and is now the default for non-IDE storage controllers.</desc>
-     </const>
-  </enum>
 
   <!--