From owner-svn-src-all@FreeBSD.ORG Mon Oct 15 13:04:29 2012 Return-Path: Delivered-To: svn-src-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 64B1E17C; Mon, 15 Oct 2012 13:04:29 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 377668FC16; Mon, 15 Oct 2012 13:04:29 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 98C0CB958; Mon, 15 Oct 2012 09:04:28 -0400 (EDT) From: John Baldwin To: Konstantin Belousov Subject: Re: svn commit: r241556 - in head/sys: kern sys Date: Mon, 15 Oct 2012 08:37:04 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p20; KDE/4.5.5; amd64; ; ) References: <201210141943.q9EJhclS029533@svn.freebsd.org> In-Reply-To: <201210141943.q9EJhclS029533@svn.freebsd.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201210150837.04943.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 15 Oct 2012 09:04:28 -0400 (EDT) Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Oct 2012 13:04:29 -0000 On Sunday, October 14, 2012 3:43:37 pm Konstantin Belousov wrote: > Author: kib > Date: Sun Oct 14 19:43:37 2012 > New Revision: 241556 > URL: http://svn.freebsd.org/changeset/base/241556 > > Log: > Add a KPI to allow to reserve some amount of space in the numvnodes > counter, without actually allocating the vnodes. The supposed use of > the getnewvnode_reserve(9) is to reclaim enough free vnodes while the > code still does not hold any resources that might be needed during the > reclamation, and to consume the slack later for getnewvnode() calls > made from the innards. After the critical block is finished, the > caller shall free any reserve left, by getnewvnode_drop_reserve(9). Can you describe an intended use-case for this? -- John Baldwin