From owner-freebsd-stable@FreeBSD.ORG Thu Aug 14 07:44:31 2008 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 32A131065692 for ; Thu, 14 Aug 2008 07:44:31 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 2062D8FC49 for ; Thu, 14 Aug 2008 07:44:31 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id EF6EC1CC0C1; Thu, 14 Aug 2008 00:44:30 -0700 (PDT) Date: Thu, 14 Aug 2008 00:44:30 -0700 From: Jeremy Chadwick To: Sergey Chumakov Message-ID: <20080814074430.GA4096@eos.sc1.parodius.com> References: <20080814093000.4842b37c@while.alkar.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080814093000.4842b37c@while.alkar.net> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-stable@freebsd.org Subject: Re: Process size. 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: Thu, 14 Aug 2008 07:44:31 -0000 On Thu, Aug 14, 2008 at 09:30:00AM +0300, Sergey Chumakov wrote: > Hello, > > FreeBSD 7.0-RELEASE-p3 #3 > > $top > ... > PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND > 36032 root 2838 44 0 1917M 1493M ucond 0 406:39 3.03% CGServer > ... > > $cat /boot/loader.conf.local > ... > kern.maxdsiz="1073741824" > kern.maxssiz="134217728" > kern.dfldsiz="1073741824" > > $limits > Resource limits (current): > ... > datasize 1048576 kB > stacksize 131072 kB > > How and why is it possible for process to grow up to 1493M and even > more? I suppose, it will be able to eat all available system memory (was > killed). Do resource limits apply to root? I wonder if it's an issue of calculation in top; top might be including page sizes and other VM-related things, while limits datasize and stacksize may only be specific to those allocated amounts. If this machine was running RELENG_7 (STABLE), it would have procstat, which could help discern where the "extra" memory is. Also: is this i386 or amd64? -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |