diff options
author | Paolo Bonzini <pbonzini@redhat.com> | 2013-02-08 14:06:11 +0100 |
---|---|---|
committer | Kevin Wolf <kwolf@redhat.com> | 2013-02-22 21:29:42 +0100 |
commit | 9e8f1835ea3ab3be83634f34c1bb8b69cd871766 (patch) | |
tree | 079db917d1d60678dd098fdf53d3b549dc82191d /include/exec/gen-icount.h | |
parent | 9a665b2b8640e464f0a778216fc2dca8d02acf33 (diff) |
block: implement BDRV_O_UNMAP
It is better to present homogeneous hardware independent of the storage
technology that is chosen on the host, hence we make discard a host
parameter; the user can choose whether to pass it down to the image
format and protocol, or to ignore it.
Using DISCARD with filesystems can cause very severe fragmentation, so it
is left default-off for now. This can change later when we implement the
"anchor" operation for efficient management of preallocated files.
There is still one choice to make: whether DISCARD has an effect on the
dirty bitmap or not. I chose yes, though there is a disadvantage: if
the guest is buggy and issues discards for data that is in use, there
will be no way to migrate storage for that guest without downgrading
the machine type to an older one.
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Diffstat (limited to 'include/exec/gen-icount.h')
0 files changed, 0 insertions, 0 deletions