From owner-freebsd-stable@FreeBSD.ORG Fri Oct 19 19:56:05 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6E8C516A421 for ; Fri, 19 Oct 2007 19:56:05 +0000 (UTC) (envelope-from rermilov@team.vega.ru) Received: from mail.vega.ru (mx1.vega.ru [87.242.77.163]) by mx1.freebsd.org (Postfix) with ESMTP id 107DB13C481 for ; Fri, 19 Oct 2007 19:55:55 +0000 (UTC) (envelope-from rermilov@team.vega.ru) Received: from [87.242.97.68] (port=60378 helo=edoofus.dev.vega.ru) by mail.vega.ru with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IixaO-0005Br-Uu; Fri, 19 Oct 2007 19:32:44 +0000 Received: from edoofus.dev.vega.ru (localhost [127.0.0.1]) by edoofus.dev.vega.ru (8.14.1/8.14.1) with ESMTP id l9JJVufj052664; Fri, 19 Oct 2007 23:31:56 +0400 (MSD) (envelope-from rermilov@team.vega.ru) Received: (from ru@localhost) by edoofus.dev.vega.ru (8.14.1/8.14.1/Submit) id l9JJVt8U052663; Fri, 19 Oct 2007 23:31:55 +0400 (MSD) (envelope-from rermilov@team.vega.ru) X-Authentication-Warning: edoofus.dev.vega.ru: ru set sender to rermilov@team.vega.ru using -f Date: Fri, 19 Oct 2007 23:31:55 +0400 From: Ruslan Ermilov To: Christopher Chen Message-ID: <20071019193155.GA40442@team.vega.ru> References: <7bc80d500710181207pe161b81j3131d370bbbbc631@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7bc80d500710181207pe161b81j3131d370bbbbc631@mail.gmail.com> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-stable@freebsd.org Subject: Re: rpc.statd--256M okay, but 1G? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Oct 2007 19:56:05 -0000 On Thu, Oct 18, 2007 at 12:07:02PM -0700, Christopher Chen wrote: > Is there a simple and easy reason why rpc.statd would mmap 1G? I've > read the FAQ and understand why it would allocate 256M, but this one > shows 1G--file.c in /usr/src/usr.sbin/rpc.statd is still set to > allocate 256M, btw. > > This is a 6.2 machine on i386, with 4G RAM, but PAE is not enabled. > That's what I would assume, that if PAE was enabled, it may change the > characteristics of that mmap (but even then, the address space of each > process would be the same...) > > The machine is a nfs client, has no exports, and has two mounts. > > Any quick thoughts? > It has been fixed in RELENG_6 in rev. 1.12.8.2 of statd.c: : revision 1.12.8.2 : date: 2007/08/12 01:46:19; author: truckman; state: Exp; lines: +1 -1 : MFC statd.c 1.15 - : The call to init_file() needs to be moved outside the loop in statd.c, : otherwise mmap() gets called multiple times, which eventually fails due : to address space exhaustion on i386. Cheers, -- Ruslan Ermilov ru@FreeBSD.org FreeBSD committer