| commit | b3b7036afbf564268ad7edc10fb28501af0709e9 | |
| author | Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com> | |
| Tue, 22 Oct 2019 11:18:01 +0000 (22 14:18 +0300) | ||
| committer | Max Reitz <mreitz@redhat.com> | |
| Mon, 28 Oct 2019 10:22:31 +0000 (28 11:22 +0100) | ||
| tree | 5e94ce5bea9282084b1fc6dfbbc7ae614c66f5b1 | treesnapshot (tar.gz zip) |
| parent | 3816edd2cb8391a782bde365d7f14705fdb2834d | commitdiff |
block/block-copy: limit copy_range_size to 16 MiB
Large copy range may imply memory allocation and large io effort, so
using 2G copy range request may be bad idea. Let's limit it to 16 MiB.
It also helps the following patch to refactor copy-with-offload
fallback to copy-with-bounce-buffer.
Note, that total memory usage of backup is still not limited, it will
be fixed in further commit.
Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Reviewed-by: Max Reitz <mreitz@redhat.com>
Message-id: 20191022111805.3432-3-vsementsov@virtuozzo.com
Signed-off-by: Max Reitz <mreitz@redhat.com>
Large copy range may imply memory allocation and large io effort, so
using 2G copy range request may be bad idea. Let's limit it to 16 MiB.
It also helps the following patch to refactor copy-with-offload
fallback to copy-with-bounce-buffer.
Note, that total memory usage of backup is still not limited, it will
be fixed in further commit.
Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Reviewed-by: Max Reitz <mreitz@redhat.com>
Message-id: 20191022111805.3432-3-vsementsov@virtuozzo.com
Signed-off-by: Max Reitz <mreitz@redhat.com>
| block/block-copy.c | diffblobblamehistory |