Rick Macklem c5128c48df VOP_COPY_FILE_RANGE: Add a COPY_FILE_RANGE_TIMEO1SEC flag
Although it is not specified in the RFCs, the concept that
the NFSv4 server should reply to an RPC request within a
reasonable time is accepted practice within the NFSv4 community.

Without this patch, the NFSv4.2 server attempts to reply to
a Copy operation within 1second by limiting the copy to
vfs.nfs.maxcopyrange bytes (default 10Mbytes). This is crude at
best, given the large variation in I/O subsystem performance.

This patch adds a kernel only flag COPY_FILE_RANGE_TIMEO1SEC
that the NFSv4.2 can specify, which tells VOP_COPY_FILE_RANGE()
to return after approximately 1 second with a partial result and
implements this in vn_generic_copy_file_range(), used by
vop_stdcopyfilerange().

Modifying the NFSv4.2 server to set this flag will be done in
a separate patch.  Also under consideration is exposing the
COPY_FILE_RANGE_TIMEO1SEC to userland for use on the FreeBSD
copy_file_range(2) syscall.

MFC after:	2 weeks
Reviewed by:	khng
Differential Revision:	https://reviews.freebsd.org/D31829
2021-09-07 17:35:26 -07:00
..
2021-08-05 23:22:02 +08:00
2021-06-07 16:45:50 -04:00
2020-11-19 02:50:48 +00:00
2021-08-10 21:27:54 -04:00
2021-08-18 08:48:27 +02:00
2020-12-04 18:56:44 +00:00
2021-04-18 11:19:15 -06:00
2021-04-12 11:42:21 -03:00
2021-09-05 12:50:15 -07:00
2021-08-10 21:27:54 -04:00
2020-11-05 15:08:56 +00:00
2021-08-08 21:54:49 -04:00
2020-11-09 00:34:23 +00:00
2021-09-03 23:13:42 -04:00
2021-04-02 15:41:51 +03:00
2021-07-28 22:00:29 -04:00
2021-08-18 08:51:26 +02:00
2021-08-05 23:22:02 +08:00
2021-08-05 23:22:02 +08:00
2021-04-18 11:14:17 -06:00
2021-09-03 22:18:51 -04:00
2021-07-24 12:52:32 -07:00