Page MenuHomeFreeBSD

linux: implement splice(2)
Needs ReviewPublic

Authored by trasz on Jun 1 2021, 3:32 PM.
Tags
None
Referenced Files
Unknown Object (File)
Nov 4 2024, 3:03 PM
Unknown Object (File)
Oct 2 2024, 12:10 PM
Unknown Object (File)
Oct 1 2024, 5:07 PM
Unknown Object (File)
Oct 1 2024, 1:40 PM
Unknown Object (File)
Sep 28 2024, 2:23 PM
Unknown Object (File)
Sep 27 2024, 1:28 PM
Unknown Object (File)
Sep 26 2024, 7:16 PM
Unknown Object (File)
Sep 25 2024, 10:18 PM

Details

Reviewers
None
Group Reviewers
Linux Emulation

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 39642
Build 36531: arc lint + arc unit

Event Timeline

trasz requested review of this revision.Jun 1 2021, 3:32 PM

Cool. Thanks for working on it. Obviously this is an "emulation" way of implementing splice(2) and not the real thing, but I like this. Do you happen to know which software requires the splice(2) call for its correct operation?

Does this have test coverage via e.g. LTP?

Does this have test coverage via e.g. LTP?

yes, also linux source at tools/testing/selftests/splice

Does this have test coverage via e.g. LTP?

yes, also linux source at tools/testing/selftests/splice

It passes?

Does this have test coverage via e.g. LTP?

yes, also linux source at tools/testing/selftests/splice

It passes?

no, copy_file_range does not allow copying to/from pipes, only between vnode backed files

What error does kern_copy_file_range return if passed pipes

What error does kern_copy_file_range return if passed pipes

EINVAL, f_vnode == NULL check

(Tinderboxed.)

hmm, why? its unusable any way, at least one fd should be a pipe