From owner-freebsd-current@FreeBSD.ORG Fri Jun 21 00:56:32 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 518B67A3; Fri, 21 Jun 2013 00:56:32 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qc0-x234.google.com (mail-qc0-x234.google.com [IPv6:2607:f8b0:400d:c01::234]) by mx1.freebsd.org (Postfix) with ESMTP id 07BB11F9F; Fri, 21 Jun 2013 00:56:31 +0000 (UTC) Received: by mail-qc0-f180.google.com with SMTP id a1so4229793qcx.11 for ; Thu, 20 Jun 2013 17:56:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=aVBLq/YeD8nefW0VC4KUyWCpESmMjkhGaGB54+Z9qmM=; b=sSiBlzelXHUlfOxY7nDdLLC2IUYsH74mIRxCLkFjIx7VnCLa2zDDfHCGRykgePWREV fXac2JI4MbEYMZ9oGfN790Y6lIMz3U72bIo6+/hF0T5fgWoLeJ2aqKM1RoTO3v+rnsV8 PoITabh/YVlCam1rILbEcyUzrAlXHy0vb1Nmvwc0Qw6psTcbwi2jGqqBJx3OiRHcNjkZ 6/V7nb9K7tTesctwJD5tVRA9LnS2PR8D6OYa1Q+Kp1DtU0JuC0yaoAgrMgrh8Z2fZnAJ S7bRhw940OYsXBouh/3HyOaRrMxr+jTqsJx3px9BmGa1B5+p2YukABB+RvODpVMWmci8 1n9g== MIME-Version: 1.0 X-Received: by 10.49.58.70 with SMTP id o6mr2543471qeq.1.1371776191560; Thu, 20 Jun 2013 17:56:31 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.5.65 with HTTP; Thu, 20 Jun 2013 17:56:31 -0700 (PDT) In-Reply-To: References: <51C1F53B.2080502@semihalf.com> Date: Thu, 20 Jun 2013 17:56:31 -0700 X-Google-Sender-Auth: LBNSwJ9y55ug__MILUNEfwgUqVI Message-ID: Subject: Re: Kernel build fails on ARM: Cannot fork: Cannot allocate memory From: Adrian Chadd To: Jeff Roberson Content-Type: text/plain; charset=ISO-8859-1 Cc: Zbyszek Bodek , freebsd-current@freebsd.org, freebsd-arm@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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, 21 Jun 2013 00:56:32 -0000 On 20 June 2013 16:56, Jeff Roberson wrote: > Just to add some more information; On my machine with 16GB of ram the > handful of recent UMA commits save about 20MB of kmem on boot. There are > 30% fewer buckets allocated. And all of the malloc zones have similar > amounts of cached space. Actually the page size malloc bucket is taking up > much less space. > > I don't know if the problem is unique to arm but I have tested x86 limited > to 512MB of ram without trouble. I will need the stats I mentioned before > to understand what has happened. Have you tried lower than 512MB? Like, 128MB? I have a 128MB -HEAD VM on i386 and it's working fine but I haven't done much digging to see how _well_ its working. I'm about to try a 64MB and 96MB VM. I'd like to go all the way down to 32MB (obviously with a cut down kernel, as GENERIC is pretty damned big!) and ensure that i386 isn't behaving poorly. There are still plenty of ARM/MIPS embedded boards that ship with 32MB (and less) RAM. I'm going to try stable/9 on 128MB of RAM soon. I know that 9.1-REL i386 + 128MB RAM results in a crash. Hopefully this stuff is better on stable/9. Thanks, Adrian