]> git.proxmox.com Git - mirror_zfs.git/commit - module/zfs/zio.c
Default zfs_max_recordsize to 16M
authorRich Ercolani <214141+rincebrain@users.noreply.github.com>
Thu, 28 Apr 2022 22:12:24 +0000 (18:12 -0400)
committerGitHub <noreply@github.com>
Thu, 28 Apr 2022 22:12:24 +0000 (15:12 -0700)
commitf2330bd1568489ae1fb16d975a5a9bcfe12ed219
tree8cc268510800aaeecccd91cee14fa186da8b9a67
parent63b18e4097cd5268cb197327ee8494ffa3dca151
Default zfs_max_recordsize to 16M

Increase the default allowed maximum recordsize from 1M to 16M.
As described in the zfs(4) man page, there are significant costs
which need to be considered before using very large blocks.
However, there are scenarios where they make good sense and
it should no longer be necessary to artificially restrict their
use behind a module option.

Note that for 32-bit platforms we continue to leave this
restriction in place due to the limited virtual address space
available (256-512MB).  On these systems only a handful
of blocks could be cached at any one time severely impacting
performance and potentially stability.

Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Reviewed-by: Alexander Motin <mav@FreeBSD.org>
Signed-off-by: Rich Ercolani <rincebrain@gmail.com>
Closes #12830
Closes #13302
man/man4/zfs.4
module/zfs/dsl_dataset.c
module/zfs/zio.c
tests/zfs-tests/tests/functional/alloc_class/alloc_class_011_neg.ksh
tests/zfs-tests/tests/functional/cli_root/zfs_create/zfs_create_008_neg.ksh
tests/zfs-tests/tests/functional/cli_root/zfs_set/zfs_set_001_neg.ksh
tests/zfs-tests/tests/functional/cli_root/zpool_create/zpool_create_023_neg.ksh