| Main index | Section 5 | Options |
Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):
tarfs_load="YES"
The preferred I/O size for tarfs filesystems can be adjusted using the vfs.tarfs.ioshift sysctl setting and tunable. Setting it to 0 will reset it to its default value. Note that changes to this setting only apply to filesystems mounted after the change.
When the backing tar file is compressed with zstd(1), I/O performance can be improved by ensuring that compressed data is broken up into multiple frames. This helps minimize unnecessary decompression work. When using bsdtar(1) to create the tar file, this can be achieved using the zstd:max-frame-size and zstd:frame-per-file options. Sensible frame sizes are powers of 2 between the system's base page size (see arch(7)) and the value of the kern.maxphys sysctl. Smaller frames will generally yield a worse compression ratio and require extra kernel memory to maintain an index, and larger frames will on average require more CPU time to access data when performing random I/O.
0x01 | Memory allocations |
0x02 | Checksum calculations |
0x04 | Filesystem operations (vfsops) |
0x08 | Path lookups |
0x10 | File operations (vnops) |
0x20 | General I/O |
0x40 | Decompression |
0x80 | Decompression index |
0x100 | Sparse file mapping |
0x200 | Bounce buffer usage |
| TARFS (5) | February 14, 2023 |
| Main index | Section 5 | Options |
Please direct any comments about this manual page service to Ben Bullock. Privacy policy.
| “ | Never write it in C if you can do it in `awk'; Never do it in `awk' if `sed' can handle it; Never use `sed' when `tr' can do the job; Never invoke `tr' when `cat' is sufficient; Avoid using `cat' whenever possible. |
” |
| — Taylor's Laws of Programming | ||