diff options
| author | bors <bors@rust-lang.org> | 2024-12-28 13:49:45 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2024-12-28 13:49:45 +0000 |
| commit | 3c1e750364012e78dcc46e5c96973fab42c7b295 (patch) | |
| tree | 5c90f5f45bb9c19a36b7840cb1eb7fd1847452a8 /tests/codegen/const-array.rs | |
| parent | 4e0bc490c60d3588f3ec0aa2eee2cf0696c7c333 (diff) | |
| parent | 96cc078878c93aa0826af3b1c40d4f238a4f4555 (diff) | |
| download | rust-3c1e750364012e78dcc46e5c96973fab42c7b295.tar.gz rust-3c1e750364012e78dcc46e5c96973fab42c7b295.zip | |
Auto merge of #134547 - SUPERCILEX:unify-copy, r=thomcc
Unify fs::copy and io::copy on Linux Currently, `fs::copy` first tries a regular file copy (via copy_file_range) and then falls back to userspace read/write copying. We should use `io::copy` instead as it tries copy_file_range, sendfile, and splice before falling back to userspace copying. This was discovered here: https://github.com/SUPERCILEX/fuc/issues/40 Perf impact: `fs::copy` will now have two additional statx calls to decide which syscall to use. I wonder if we should get rid of the statx calls and only continue down the next fallback when the relevant syscalls say the FD isn't supported.
Diffstat (limited to 'tests/codegen/const-array.rs')
0 files changed, 0 insertions, 0 deletions