From owner-freebsd-hackers@FreeBSD.ORG Sat Oct 2 16:06:13 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 951F216A4CE for ; Sat, 2 Oct 2004 16:06:13 +0000 (GMT) Received: from node15.coopprint.com (node15.cooperativeprinting.com [208.4.77.15]) by mx1.FreeBSD.org (Postfix) with SMTP id DA53143D45 for ; Sat, 2 Oct 2004 16:06:12 +0000 (GMT) (envelope-from ryans@gamersimpact.com) Received: (qmail 50875 invoked by uid 0); 2 Oct 2004 16:05:41 -0000 Received: from unknown (HELO ?192.168.0.5?) (63.231.165.205) by node15.coopprint.com with SMTP; 2 Oct 2004 16:05:41 -0000 Message-ID: <415ED1F8.7030705@gamersimpact.com> Date: Sat, 02 Oct 2004 11:06:16 -0500 From: Ryan Sommers User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jan Srzednicki References: <20041002114846.GA23339@miranda.expro.pl> In-Reply-To: <20041002114846.GA23339@miranda.expro.pl> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: hackers@freebsd.org Subject: Re: Wired memory monitoring X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Oct 2004 16:06:13 -0000 Jan Srzednicki wrote: >Hello, > >I am investigating some VM issues on FreeBSD. I have noticed that wired >memory grows quite rapidly on forking lots of processes. After those >processes exit, it drops a bit, but still can use about 100MB after >launching 3000 processes. I think it's not a leak, as subsequent forks >don't cause it to grow noticeably. > >I'm rather curious what eats all that memory. sysctl vm.zone shows some >high values, but they're are not high in memory usage terms, even >considering 50% (or so) efficiency of the slab allocator. > >The question is, are there any other memory inspecting tools that would >allow me to see where is all that wired memory? And, are there any ways >to control it's behaviour (eg. to free unused per-process structures and >data)? > >greetings, > > Wouldn't that be the zone allocator grabbing pages from the free list and adding them to non-pagable per process structures? -- Ryan Sommers ryans@gamersimpact.com