diff options
author | Kevin Wolf <kwolf@redhat.com> | 2013-03-26 17:49:56 +0100 |
---|---|---|
committer | Stefan Hajnoczi <stefanha@redhat.com> | 2013-03-28 11:52:42 +0100 |
commit | 17a71e58238138c3f02be7e9f5dc8de5d72a9a9d (patch) | |
tree | e6ceb05281a72aacaf0bb543a13a39e766e4836b /default-configs | |
parent | 9ee6439e27d15c528fde6d9da1e4c238a23b6b7a (diff) |
qcow2: Handle dependencies earlier
Handling overlapping allocations isn't just a detail of cluster
allocation. It is rather one of three ways to get the host cluster
offset for a write request:
1. If a request overlaps an in-flight allocations, the cluster offset
can be taken from there (this is what handle_dependencies will evolve
into) or the request must just wait until the allocation has
completed. Accessing the L2 is not valid in this case, it has
outdated information.
2. Outside overlapping areas, check the clusters that can be written to
as they are, with no COW involved.
3. If a COW is required, allocate new clusters
Changing the code to reflect this doesn't change the behaviour because
overlaps cannot exist for clusters that are kept in step 2. It does
however make it easier for later patches to work on clusters that belong
to an allocation that is still in flight.
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Diffstat (limited to 'default-configs')
0 files changed, 0 insertions, 0 deletions