summaryrefslogtreecommitdiff
path: root/static/netbsd/man4/viomb.4 4.html
diff options
context:
space:
mode:
Diffstat (limited to 'static/netbsd/man4/viomb.4 4.html')
-rw-r--r--static/netbsd/man4/viomb.4 4.html70
1 files changed, 0 insertions, 70 deletions
diff --git a/static/netbsd/man4/viomb.4 4.html b/static/netbsd/man4/viomb.4 4.html
deleted file mode 100644
index ed46c66a..00000000
--- a/static/netbsd/man4/viomb.4 4.html
+++ /dev/null
@@ -1,70 +0,0 @@
-<table class="head">
- <tr>
- <td class="head-ltitle">VIOMB(4)</td>
- <td class="head-vol">Device Drivers Manual</td>
- <td class="head-rtitle">VIOMB(4)</td>
- </tr>
-</table>
-<div class="manual-text">
-<section class="Sh">
-<h1 class="Sh" id="NAME"><a class="permalink" href="#NAME">NAME</a></h1>
-<p class="Pp"><code class="Nm">viomb</code> &#x2014; <span class="Nd">VirtIO
- memory ballooning driver</span></p>
-</section>
-<section class="Sh">
-<h1 class="Sh" id="SYNOPSIS"><a class="permalink" href="#SYNOPSIS">SYNOPSIS</a></h1>
-<p class="Pp"><code class="Cd">virtio* at pci? dev ? function ?</code>
- <br/>
- <code class="Cd">viomb* at virtio?</code></p>
-</section>
-<section class="Sh">
-<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1>
-<p class="Pp"><a class="Xr">virtio(4)</a> defines an interface for efficient,
- standard, and extensible I/O between the hypervisor and the virtual machine.
- The <code class="Nm">viomb</code> driver supports the virtio-compliant
- memory ballooning device.</p>
-<p class="Pp">Memory ballooning works as follows:</p>
-<p class="Pp"></p>
-<ol class="Bl-enum Bl-compact">
- <li>The host operator requests a guest to return some amount of memory to the
- host (via e.g. Qemu monitor balloon command).</li>
- <li>The hypervisor sends the request via VirtIO memory ballooning device.</li>
- <li>The guest <code class="Nm">viomb</code> driver requests allocation of that
- amount of physical memory from the <span class="Ux">NetBSD</span> memory
- management system.</li>
- <li>The <code class="Nm">viomb</code> device tells the hypervisor the guest
- physical memory address of the allocated memory via VirtIO memory
- ballooning device.</li>
-</ol>
-<p class="Pp">The sysctl node <code class="Li">hw.viomb.npages</code> shows the
- requested number of memory pages to return to the hypervisor, while
- <code class="Li">hw.viomb.actual</code> shows the actual number of memory
- pages that are already returned to the hypervisor.</p>
-</section>
-<section class="Sh">
-<h1 class="Sh" id="SEE_ALSO"><a class="permalink" href="#SEE_ALSO">SEE
- ALSO</a></h1>
-<p class="Pp"><a class="Xr">virtio(4)</a>, <a class="Xr">sysctl(8)</a>,
- <a class="Xr">x86/balloon(4)</a></p>
-<p class="Pp"></p>
-<p class="Pp"><cite class="Rs"><span class="RsA">Rusty Russell, IBM
- Corporation</span>, <span class="RsT">Virtio PCI Card Specification</span>,
- <a class="RsU" href="http://ozlabs.org/~rusty/virtio-spec/">http://ozlabs.org/~rusty/virtio-spec/</a>.</cite></p>
-</section>
-<section class="Sh">
-<h1 class="Sh" id="HISTORY"><a class="permalink" href="#HISTORY">HISTORY</a></h1>
-<p class="Pp">The <code class="Nm">viomb</code> device driver appeared in
- <span class="Ux">NetBSD 6.0</span>.</p>
-</section>
-<section class="Sh">
-<h1 class="Sh" id="BUGS"><a class="permalink" href="#BUGS">BUGS</a></h1>
-<p class="Pp">The userland interface should be same as the Xen ballooning
- device.</p>
-</section>
-</div>
-<table class="foot">
- <tr>
- <td class="foot-date">August 25, 2020</td>
- <td class="foot-os">NetBSD 10.1</td>
- </tr>
-</table>