diff options
author | Amir Goldstein <amir73il@gmail.com> | 2016-09-23 11:38:12 +0300 |
---|---|---|
committer | Miklos Szeredi <mszeredi@redhat.com> | 2016-12-16 13:02:54 +0300 |
commit | 2ea98466491b7609ace297647b07c28d99ef3722 (patch) | |
tree | 12ffc06a7407573c47653ecc5bbcee4103616709 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | 31c3a7069593b072bd57192b63b62f9a7e994e9a (diff) | |
download | linux-2ea98466491b7609ace297647b07c28d99ef3722.tar.xz |
ovl: use vfs_clone_file_range() for copy up if possible
When copying up within the same fs, try to use vfs_clone_file_range().
This is very efficient when lower and upper are on the same fs
with file reflink support. If vfs_clone_file_range() fails for any
reason, copy up falls back to the regular data copy code.
Tested correct behavior when lower and upper are on:
1. same ext4 (copy)
2. same xfs + reflink patches + mkfs.xfs (copy)
3. same xfs + reflink patches + mkfs.xfs -m reflink=1 (reflink)
4. different xfs + reflink patches + mkfs.xfs -m reflink=1 (copy)
For comparison, on my laptop, xfstest overlay/001 (copy up of large
sparse files) takes less than 1 second in the xfs reflink setup vs.
25 seconds on the rest of the setups.
Signed-off-by: Amir Goldstein <amir73il@gmail.com>
Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions