| commit | 78cae78dbcf94a151203ab5c6e418d9d9094a59e | |
| author | Kevin Wolf <kwolf@redhat.com> | |
| Thu, 30 Apr 2020 13:30:05 +0000 (30 15:30 +0200) | ||
| committer | Kevin Wolf <kwolf@redhat.com> | |
| Fri, 8 May 2020 11:26:35 +0000 (8 13:26 +0200) | ||
| tree | 712dc2a5ef3961a1dc75f74a387cc4190efecea9 | treesnapshot (tar.gz zip) |
| parent | 4823cde58eb507fcdcc0225b087343439a6cb43c | commitdiff |
vmdk: Don't update L2 table for zero write on zero cluster
If a cluster is already zeroed, we don't have to call vmdk_L2update(),
which is rather slow because it flushes the image file.
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Message-Id: <20200430133007.170335-5-kwolf@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
If a cluster is already zeroed, we don't have to call vmdk_L2update(),
which is rather slow because it flushes the image file.
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Message-Id: <20200430133007.170335-5-kwolf@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
| block/vmdk.c | diffblobblamehistory |