Date: Sat, 01 Aug 2020 00:16:30 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 248401] net/rsync xxh3 (and xxh128) hashes are unavailable (low priority) Message-ID: <bug-248401-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D248401 Bug ID: 248401 Summary: net/rsync xxh3 (and xxh128) hashes are unavailable (low priority) Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: rodrigo@FreeBSD.org Reporter: dewayne@heuristicsystems.com.au Assignee: rodrigo@FreeBSD.org Flags: maintainer-feedback?(rodrigo@FreeBSD.org) Now that xxh hashes with their significant speed advantage are available and documented for rsync, I successfully performed (on FreeBSD12.1 amd64 and x8= 6) # rsync -AXv --cc=3Dxxh64 /tmp/file.txt /tmp/b2/=20 YAY! (Aside: for the reader, xxh64 is synonomous with xxhash) but # rsync -AXv --cc=3Dxxh3 /tmp/file.txt /tmp/b2 unknown checksum name: xxh3 rsync error: requested action not supported (code 4) at checksum.c(86) [client=3D3.2.2] and=20 # rsync -AXv --cc=3Dxxh128 /tmp/file.txt /tmp/b2 performed similarly. As ~20% of devices are still 32bit (so would benefit from xxh3), based on t= he performance improvement suggested by=20 https://cyan4973.github.io/xxHash/=20 we look forward to this enhancement. And as xxh64 functions, this PR shoul= d be a low priority. If it wasn't documented in the man page, I think rsync functions as intended ;) --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-248401-7788>