From owner-freebsd-questions@freebsd.org Fri Feb 17 16:52:11 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E2019CE36DD for ; Fri, 17 Feb 2017 16:52:11 +0000 (UTC) (envelope-from freebsd@qeng-ho.org) Received: from bede.home.qeng-ho.org (bede.qeng-ho.org [217.155.128.241]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "fileserver.home.qeng-ho.org", Issuer "fileserver.home.qeng-ho.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7E8AF16CE for ; Fri, 17 Feb 2017 16:52:10 +0000 (UTC) (envelope-from freebsd@qeng-ho.org) Received: from arthur.home.qeng-ho.org (arthur.home.qeng-ho.org [172.23.1.2]) by bede.home.qeng-ho.org (8.15.2/8.15.2) with ESMTP id v1HGLrwG025203; Fri, 17 Feb 2017 16:21:53 GMT (envelope-from freebsd@qeng-ho.org) Subject: Re: pf can't get memory for tables To: Scott Bennett , freebsd-questions@freebsd.org References: <201702170919.v1H9J45t015787@sdf.org> From: Arthur Chance Message-ID: <1cd15985-dcf5-673f-9517-63575c8fbf1e@qeng-ho.org> Date: Fri, 17 Feb 2017 16:21:53 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: <201702170919.v1H9J45t015787@sdf.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Feb 2017 16:52:12 -0000 On 17/02/2017 09:19, Scott Bennett wrote: [much snippage] > After > puzzling over this turn of events on my screen for several seconds...aha! > The machine has only 4 GB of RAM, so a long while back I added > > vm.kmem_size_max=805306368 > > to /boot/loader.conf in order to limit the tendency at the time for ZFS to > take over everything with a growing ARC. Unfortunately, vm.kmem_size_max > is one of those tunables that can only be set at boot time, so I can't easily > experiment with increasing the value. If you want to control the ARC size, surely setting vfs.zfs.arc_max in /boot/loader.conf is more specific than vm.kmem_size_max? Unfortunately that's a boot time tunable as well. -- By June 1949, people had begun to realize that it was not so easy to get a program right as had at one time appeared. It was on one of my journeys between the EDSAC room and the punching equipment that the realization came over me with full force that a good part of the remainder of my life was going to be spent in finding errors in my own programs. -- Maurice Wilkes