Features/QED: Difference between revisions

From QEMU
No edit summary
No edit summary
(10 intermediate revisions by 5 users not shown)
Line 1: Line 1:
= Overview =
QED is an image format (like qcow2, vmdk, etc) that supports backing files and sparse images.
= Status =
= Status =


* '''Base QED is in qemu.git''' since [http://git.qemu.org/qemu.git/commit/?id=75411d236d93d79d8052e0116c3eeebe23e2778b 2010-12-17] and will form part of QEMU 0.14.
* '''Base QED is in qemu.git''' since [http://git.qemu.org/qemu.git/commit/?id=75411d236d93d79d8052e0116c3eeebe23e2778b 2010-12-17] and will form part of QEMU 0.14.
* Zero cluster patches on mailing list, qemu-iotests under development.
* Merge plan for additional features:
* Upcoming image streaming patches are prepared.
** Zero clusters [submitted].
** Periodic dirty flag flush [submitted].
** Image streaming [in preparation].


= Features =
= Features =
Line 16: Line 22:


= Current work =
= Current work =
* [[Features/QED/OutstandingCommunityRequests Outstanding community requests]]
* [[Features/QED/OutstandingWork|Outstanding work]]


= Future Features =
= Future Features =
* [[Features/QED/Streaming|Streaming]]
* [[Features/QED/Streaming|Streaming]]
* [[Features/QED/OnlineDefrag|Online defragmentation]]
* [[Features/QED/OnlineDefrag|Online defragmentation]]
* [[Features/QED/Trim|Trim]]
* [[Features/QED/ParallelSubmission|Parallel submission]]
* [[Features/QED/ParallelSubmission|Parallel submission]]
* [[Features/QED/ScanAvoidance|Meta-data scan avoidance]]
* [[Features/QED/ScanAvoidance|Meta-data scan avoidance]]
[[Category:Obsolete feature pages]]

Revision as of 14:45, 11 October 2016

Overview

QED is an image format (like qcow2, vmdk, etc) that supports backing files and sparse images.

Status

  • Base QED is in qemu.git since 2010-12-17 and will form part of QEMU 0.14.
  • Merge plan for additional features:
    • Zero clusters [submitted].
    • Periodic dirty flag flush [submitted].
    • Image streaming [in preparation].

Features

  • Open specification
  • Fully asynchronous I/O path
  • Strong data integrity due to simple design
  • Backing files
    • Backing files may be smaller than the QED image
  • Sparse files
    • Retains sparseness over non-sparse channels (e.g. HTTP)

Current work

Future Features