From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 14:38:05 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 16256106564A; Fri, 24 Aug 2012 14:38:05 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.59.238]) by mx1.freebsd.org (Postfix) with ESMTP id C1EE58FC12; Fri, 24 Aug 2012 14:38:03 +0000 (UTC) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 83FB57300A; Fri, 24 Aug 2012 16:57:08 +0200 (CEST) Date: Fri, 24 Aug 2012 16:57:08 +0200 From: Luigi Rizzo To: Alan Cox Message-ID: <20120824145708.GA16557@onelab2.iet.unipi.it> References: <20120822120105.GA63763@onelab2.iet.unipi.it> <20120823163145.GA3999@onelab2.iet.unipi.it> <50366398.2070700@rice.edu> <20120823174504.GB4820@onelab2.iet.unipi.it> <50371485.1020409@rice.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <50371485.1020409@rice.edu> User-Agent: Mutt/1.4.2.3i Cc: alc@freebsd.org, current@freebsd.org Subject: Re: less aggressive contigmalloc ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Aug 2012 14:38:05 -0000 On Fri, Aug 24, 2012 at 12:43:33AM -0500, Alan Cox wrote: > On 08/23/2012 12:45, Luigi Rizzo wrote: > >On Thu, Aug 23, 2012 at 12:08:40PM -0500, Alan Cox wrote: > >... > >>>yes i do see that. > >>> > >>>Maybe less aggressive with M_NOWAIT but still kills processes. > >>Are you compiling world with MALLOC_PRODUCTION? The latest version of > >whatever the default is. But: > > > >>jemalloc uses significantly more memory when debugging options are > >>enabled. This first came up in a thread titled "10-CURRENT and swap > >>usage" back in June. > >> > >>Even at its most aggressive, M_WAITOK, contigmalloc() does not directly > >>kill processes. If process death coincides with the use of > >>contigmalloc(), then it is simply the result of earlier, successful > >>contigmalloc() calls, or for that matter any other physical memory > >>allocation calls, having depleted the pool of free pages to the point > >>that the page daemon runs and invokes vm_pageout_oom(). > >does it mean that those previous allocations relied on memory overbooking ? > > Yes. > > >Is there a way to avoid that, then ? > > I believe that malloc()'s default minimum allocation size is 4MB. You > could reduce that. > > Alternatively, you can enable MALLOC_PRODUCTION. i tried this, and as others mentioned it makes life better and reduces the problem but contigmalloc still triggers random process kills. Thanks for the hints. cheers luigi