Attempt to access the file using mmap(2), rather than I/O system calls (read(2), write(2)). Currently, use of mmap(2) is attempted only for a file opened for reading.
I'm very skeptical that this actually makes things faster. For one, zstd is definitely going to be CPU bound rather than I/O bound. But even if it wasn't, there shouldn't be a performance benefit to reading a file sequentially using mmap compared to reading it sequentially using read, which you can easily verify yourself by writing a small program that just reads files both ways.
If anyone is interested in the clearlinux optimized zstd build config ( imho it is useful for the 1.5.5 building )
https://github.com/clearlinux-pkgs/zstd/blob/main/zstd.spec
( CFLAGS, 4 patch )