From owner-freebsd-fs@FreeBSD.ORG Tue May 20 08:40:01 2014 Return-Path: Delivered-To: freebsd-fs@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DB0A9202 for ; Tue, 20 May 2014 08:40:01 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C84332C28 for ; Tue, 20 May 2014 08:40:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s4K8e1iI098237 for ; Tue, 20 May 2014 08:40:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s4K8e1NP098236; Tue, 20 May 2014 08:40:01 GMT (envelope-from gnats) Date: Tue, 20 May 2014 08:40:01 GMT Message-Id: <201405200840.s4K8e1NP098236@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org Cc: From: "Steven Hartland" Subject: Re: kern/189865: [zfs] [patch] zfs_dirty_data_max{, _max, _percent} not exported as loader tunables Reply-To: "Steven Hartland" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 May 2014 08:40:01 -0000 The following reply was made to PR kern/189865; it has been noted by GNATS. From: "Steven Hartland" To: , Cc: Subject: Re: kern/189865: [zfs] [patch] zfs_dirty_data_max{,_max,_percent} not exported as loader tunables Date: Tue, 20 May 2014 09:38:04 +0100 Exposing zfs_dirty_data_max directly doesn't make sense as its a calculated value based off zfs_dirty_data_max_percent% of all memory and capped at zfs_dirty_data_max_max. Given this it could be limited via setting zfs_dirty_data_max_max. The following could be exposed:- zfs_dirty_data_max_max zfs_dirty_data_max_percent zfs_dirty_data_sync zfs_delay_min_dirty_percent zfs_delay_scale Would that forfull your requirement? Regards Steve