mirror of
https://git.proxmox.com/git/mirror_zfs.git
synced 2026-05-30 18:56:23 +03:00
Add TRIM support
UNMAP/TRIM support is a frequently-requested feature to help prevent performance from degrading on SSDs and on various other SAN-like storage back-ends. By issuing UNMAP/TRIM commands for sectors which are no longer allocated the underlying device can often more efficiently manage itself. This TRIM implementation is modeled on the `zpool initialize` feature which writes a pattern to all unallocated space in the pool. The new `zpool trim` command uses the same vdev_xlate() code to calculate what sectors are unallocated, the same per- vdev TRIM thread model and locking, and the same basic CLI for a consistent user experience. The core difference is that instead of writing a pattern it will issue UNMAP/TRIM commands for those extents. The zio pipeline was updated to accommodate this by adding a new ZIO_TYPE_TRIM type and associated spa taskq. This new type makes is straight forward to add the platform specific TRIM/UNMAP calls to vdev_disk.c and vdev_file.c. These new ZIO_TYPE_TRIM zios are handled largely the same way as ZIO_TYPE_READs or ZIO_TYPE_WRITEs. This makes it possible to largely avoid changing the pipieline, one exception is that TRIM zio's may exceed the 16M block size limit since they contain no data. In addition to the manual `zpool trim` command, a background automatic TRIM was added and is controlled by the 'autotrim' property. It relies on the exact same infrastructure as the manual TRIM. However, instead of relying on the extents in a metaslab's ms_allocatable range tree, a ms_trim tree is kept per metaslab. When 'autotrim=on', ranges added back to the ms_allocatable tree are also added to the ms_free tree. The ms_free tree is then periodically consumed by an autotrim thread which systematically walks a top level vdev's metaslabs. Since the automatic TRIM will skip ranges it considers too small there is value in occasionally running a full `zpool trim`. This may occur when the freed blocks are small and not enough time was allowed to aggregate them. An automatic TRIM and a manual `zpool trim` may be run concurrently, in which case the automatic TRIM will yield to the manual TRIM. Reviewed-by: Jorgen Lundman <lundman@lundman.net> Reviewed-by: Tim Chase <tim@chase2k.com> Reviewed-by: Matt Ahrens <mahrens@delphix.com> Reviewed-by: George Wilson <george.wilson@delphix.com> Reviewed-by: Serapheim Dimitropoulos <serapheim@delphix.com> Contributions-by: Saso Kiselkov <saso.kiselkov@nexenta.com> Contributions-by: Tim Chase <tim@chase2k.com> Contributions-by: Chunwei Chen <tuxoko@gmail.com> Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> Closes #8419 Closes #598
This commit is contained in:
Brian Behlendorf
@@ -14,7 +14,7 @@
|
||||
.\" CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your
|
||||
.\" own identifying information:
|
||||
.\" Portions Copyright [yyyy] [name of copyright owner]
|
||||
.TH ZFS-MODULE-PARAMETERS 5 "Feb 8, 2019"
|
||||
.TH ZFS-MODULE-PARAMETERS 5 "Feb 15, 2019"
|
||||
.SH NAME
|
||||
zfs\-module\-parameters \- ZFS module parameters
|
||||
.SH DESCRIPTION
|
||||
@@ -1532,6 +1532,30 @@ See the section "ZFS I/O SCHEDULER".
|
||||
Default value: \fB10\fR.
|
||||
.RE
|
||||
|
||||
.sp
|
||||
.ne 2
|
||||
.na
|
||||
\fBzfs_vdev_trim_max_active\fR (int)
|
||||
.ad
|
||||
.RS 12n
|
||||
Maximum trim/discard I/Os active to each device.
|
||||
See the section "ZFS I/O SCHEDULER".
|
||||
.sp
|
||||
Default value: \fB2\fR.
|
||||
.RE
|
||||
|
||||
.sp
|
||||
.ne 2
|
||||
.na
|
||||
\fBzfs_vdev_trim_min_active\fR (int)
|
||||
.ad
|
||||
.RS 12n
|
||||
Minimum trim/discard I/Os active to each device.
|
||||
See the section "ZFS I/O SCHEDULER".
|
||||
.sp
|
||||
Default value: \fB1\fR.
|
||||
.RE
|
||||
|
||||
.sp
|
||||
.ne 2
|
||||
.na
|
||||
@@ -1619,6 +1643,12 @@ _
|
||||
_
|
||||
512 ZFS_DEBUG_SET_ERROR
|
||||
Enable SET_ERROR and dprintf entries in the debug log.
|
||||
_
|
||||
1024 ZFS_DEBUG_INDIRECT_REMAP
|
||||
Verify split blocks created by device removal.
|
||||
_
|
||||
2048 ZFS_DEBUG_TRIM
|
||||
Verify TRIM ranges are always within the allocatable range tree.
|
||||
.TE
|
||||
.sp
|
||||
* Requires debug build.
|
||||
@@ -2341,6 +2371,82 @@ value of 75% will create a maximum of one thread per cpu.
|
||||
Default value: \fB75\fR%.
|
||||
.RE
|
||||
|
||||
.sp
|
||||
.ne 2
|
||||
.na
|
||||
\fBzfs_trim_extent_bytes_max\fR (unsigned int)
|
||||
.ad
|
||||
.RS 12n
|
||||
Maximum size of TRIM command. Ranges larger than this will be split in to
|
||||
chunks no larger than \fBzfs_trim_extent_bytes_max\fR bytes before being
|
||||
issued to the device.
|
||||
.sp
|
||||
Default value: \fB134,217,728\fR.
|
||||
.RE
|
||||
|
||||
.sp
|
||||
.ne 2
|
||||
.na
|
||||
\fBzfs_trim_extent_bytes_min\fR (unsigned int)
|
||||
.ad
|
||||
.RS 12n
|
||||
Minimum size of TRIM commands. TRIM ranges smaller than this will be skipped
|
||||
unless they're part of a larger range which was broken in to chunks. This is
|
||||
done because it's common for these small TRIMs to negatively impact overall
|
||||
performance. This value can be set to 0 to TRIM all unallocated space.
|
||||
.sp
|
||||
Default value: \fB32,768\fR.
|
||||
.RE
|
||||
|
||||
.sp
|
||||
.ne 2
|
||||
.na
|
||||
\fBzfs_trim_metaslab_skip\fR (unsigned int)
|
||||
.ad
|
||||
.RS 12n
|
||||
Skip uninitialized metaslabs during the TRIM process. This option is useful
|
||||
for pools constructed from large thinly-provisioned devices where TRIM
|
||||
operations are slow. As a pool ages an increasing fraction of the pools
|
||||
metaslabs will be initialized progressively degrading the usefulness of
|
||||
this option. This setting is stored when starting a manual TRIM and will
|
||||
persist for the duration of the requested TRIM.
|
||||
.sp
|
||||
Default value: \fB0\fR.
|
||||
.RE
|
||||
|
||||
.sp
|
||||
.ne 2
|
||||
.na
|
||||
\fBzfs_trim_queue_limit\fR (unsigned int)
|
||||
.ad
|
||||
.RS 12n
|
||||
Maximum number of queued TRIMs outstanding per leaf vdev. The number of
|
||||
concurrent TRIM commands issued to the device is controlled by the
|
||||
\fBzfs_vdev_trim_min_active\fR and \fBzfs_vdev_trim_max_active\fR module
|
||||
options.
|
||||
.sp
|
||||
Default value: \fB10\fR.
|
||||
.RE
|
||||
|
||||
.sp
|
||||
.ne 2
|
||||
.na
|
||||
\fBzfs_trim_txg_batch\fR (unsigned int)
|
||||
.ad
|
||||
.RS 12n
|
||||
The number of transaction groups worth of frees which should be aggregated
|
||||
before TRIM operations are issued to the device. This setting represents a
|
||||
trade-off between issuing larger, more efficient TRIM operations and the
|
||||
delay before the recently trimmed space is available for use by the device.
|
||||
.sp
|
||||
Increasing this value will allow frees to be aggregated for a longer time.
|
||||
This will result is larger TRIM operations and potentially increased memory
|
||||
usage. Decreasing this value will have the opposite effect. The default
|
||||
value of 32 was determined to be a reasonable compromise.
|
||||
.sp
|
||||
Default value: \fB32\fR.
|
||||
.RE
|
||||
|
||||
.sp
|
||||
.ne 2
|
||||
.na
|
||||
@@ -2364,6 +2470,19 @@ Flush dirty data to disk at least every N seconds (maximum txg duration)
|
||||
Default value: \fB5\fR.
|
||||
.RE
|
||||
|
||||
.sp
|
||||
.ne 2
|
||||
.na
|
||||
\fBzfs_vdev_aggregate_trim\fR (int)
|
||||
.ad
|
||||
.RS 12n
|
||||
Allow TRIM I/Os to be aggregated. This is normally not helpful because
|
||||
the extents to be trimmed will have been already been aggregated by the
|
||||
metaslab. This option is provided for debugging and performance analysis.
|
||||
.sp
|
||||
Default value: \fB0\fR.
|
||||
.RE
|
||||
|
||||
.sp
|
||||
.ne 2
|
||||
.na
|
||||
|
||||
Reference in New Issue
Block a user