[Bug 255523] vn_generic_copy_file_range copies holes to EOF slowly
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Sat May 1 22:49:00 UTC 2021
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255523
Rick Macklem <rmacklem at FreeBSD.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|New |Open
--- Comment #3 from Rick Macklem <rmacklem at FreeBSD.org> ---
vn_generic_copy_file_range() was coded the way it is,
since UFS (the only file system type I use/test on)
always allocates a data block (all 0 bytes) at the
end of the file.
--> Never has a hole extending to EOF.
I've attached a patch that tries to handle the
hole to EOF case.
Maybe you can test it?
Btw, the data size in the copy loop is pegged
at whatever the file system uses as a block size,
capped at 1Mbyte. This implies that interrupting
signals will be handled quickly.
--> Recall that read(2)/write(2) ignore signals,
except for the weird NFS "intr" mount option case.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-bugs
mailing list