diff options
| author | Tom Caputi <[email protected]> | 2018-12-18 17:47:33 -0500 |
|---|---|---|
| committer | Brian Behlendorf <[email protected]> | 2018-12-18 14:47:33 -0800 |
| commit | 00f198de6b6ac663926bff2666d956a61cea85db (patch) | |
| tree | 77901d675e9a2ed3368eefc85f6fc6587a80adcc /module/zfs | |
| parent | c66401fae036b22ecb3fa9af3337e1f9ecffb5e7 (diff) | |
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 <[email protected]>
Reviewed-by: Brian Behlendorf <[email protected]>
Signed-off-by: Tom Caputi <[email protected]>
Closes #8212
Diffstat (limited to 'module/zfs')
| -rw-r--r-- | module/zfs/dsl_pool.c | 5 |
1 files changed, 3 insertions, 2 deletions
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"); |