From: Tom Caputi Date: Tue, 18 Dec 2018 22:47:33 +0000 (-0500) Subject: Fix zfs_dirty_data_sync_percent documentation X-Git-Tag: zfs-0.8.0-rc3~26 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=00f198de6b6ac663926bff2666d956a61cea85db;p=zfs Fix zfs_dirty_data_sync_percent documentation In dfbe2675 zfs_dirty_data_sync was changed to a new tunable named zfs_dirty_data_sync_percent. Unfortunately, the module parameter documentation is the code was not updated accordingly. This patch simply corrects that. Reviewed-by: George Melikov Reviewed-by: Brian Behlendorf Signed-off-by: Tom Caputi Closes #8212 --- diff --git a/module/zfs/dsl_pool.c b/module/zfs/dsl_pool.c index b940382d1..e159a5d1b 100644 --- a/module/zfs/dsl_pool.c +++ b/module/zfs/dsl_pool.c @@ -83,7 +83,7 @@ * zfs_dirty_data_max determines the dirty space limit. Once that value is * exceeded, new writes are halted until space frees up. * - * The zfs_dirty_data_sync tunable dictates the threshold at which we + * The zfs_dirty_data_sync_percent tunable dictates the threshold at which we * ensure that there is a txg syncing (see the comment in txg.c for a full * description of transaction group stages). * @@ -1350,7 +1350,8 @@ MODULE_PARM_DESC(zfs_dirty_data_max_max, "zfs_dirty_data_max upper bound in bytes"); module_param(zfs_dirty_data_sync_percent, int, 0644); -MODULE_PARM_DESC(zfs_dirty_data_sync, "sync txg when this much dirty data"); +MODULE_PARM_DESC(zfs_dirty_data_sync_percent, + "dirty data txg sync threshold as a percentage of zfs_dirty_data_max"); module_param(zfs_delay_scale, ulong, 0644); MODULE_PARM_DESC(zfs_delay_scale, "how quickly delay approaches infinity");