Features/Asynchronous NBD: Difference between revisions
(Created page with '== Summary == Supporting asynchronous I/O in the NBD block device and qemu-nbd server makes it easier to use high-performance remote storage. == Owner == * Name: [[User:Paolo …') |
m (moved Features-Done/Asynchronous NBD to Features/Asynchronous NBD over redirect) |
||
| (4 intermediate revisions by the same user not shown) | |||
| Line 14: | Line 14: | ||
== Status == | == Status == | ||
Committed. | |||
== Links == | == Links == | ||
* [http://github.com/bonzini/qemu/commits/nbd-trim git tree] (branch nbd-trim, for the client) | * [http://github.com/bonzini/qemu/commits/nbd-trim git tree] (branch nbd-trim, for the client) | ||
* [http://github.com/bonzini/qemu/commits/split-main-loop git tree] (branch split-main-loop, for the server) | * [http://github.com/bonzini/qemu/commits/split-main-loop git tree] (branch split-main-loop, for the server) | ||
[[Category:Completed feature pages]] | |||
Latest revision as of 14:56, 11 October 2016
Summary
Supporting asynchronous I/O in the NBD block device and qemu-nbd server makes it easier to use high-performance remote storage.
Owner
- Name: Paolo Bonzini
- Email: pbonzini@redhat.com
Description
The NBD block device and qemu-nbd server provide a simple base for using remote storage within QEMU. NBD can also be coupled with other features such as streaming or copy-on-read. However, the NBD implementation in QEMU is entirely synchronous, thus limiting guest performance and being hardly applicable when multiple guests use the same NBD image (for example as backing storage for QCOW or QED).
Status
Committed.