From owner-freebsd-stable@FreeBSD.ORG Fri Mar 23 00:11:33 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 51D9B16A401 for ; Fri, 23 Mar 2007 00:11:33 +0000 (UTC) (envelope-from michael.schuh@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.247]) by mx1.freebsd.org (Postfix) with ESMTP id 098F913C455 for ; Fri, 23 Mar 2007 00:11:32 +0000 (UTC) (envelope-from michael.schuh@gmail.com) Received: by an-out-0708.google.com with SMTP id c24so1004419ana for ; Thu, 22 Mar 2007 17:11:32 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=Ws72zr/xgcMwbZ1Qk0J50sbFNbGP5umdpsfptfRc7GgBNGmyR0V/cq4ohK1H0SbrG50c9z3ahuDG+I6gAtdaysqzvI9/a9HhDP+7KmLfbcj5y30782w6ECc4HFrn/LTNknEHqnXV1cfa/Qn/cZpvSnU+UPRgl9NH8IvI881RwYA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=FCcCqa8t5Xn7wViFl5AR/5lNwBPkUpAKNAsofJPzr99HUEsJyhYWCLEJKxB95wrk+6HONaE9QY0CCI0f9vAYopf6GQbQ8zGXsqpWr2Dhq06QMu0q/S9MLEC9+0iULUMsgCZXb9ZQUWWuGsuBMdw6lcGdUG7C2V1mLywuMNBVZjE= Received: by 10.100.128.8 with SMTP id a8mr2137648and.1174608091972; Thu, 22 Mar 2007 17:01:31 -0700 (PDT) Received: by 10.100.174.20 with HTTP; Thu, 22 Mar 2007 17:01:31 -0700 (PDT) Message-ID: <1dbad3150703221701h1f65f3b6md74996d825f97fcd@mail.gmail.com> Date: Fri, 23 Mar 2007 01:01:31 +0100 From: "Michael Schuh" To: "Chuck Swiger" In-Reply-To: <9363AFA5-0DEF-428A-A6D4-E04A4A414F0B@mac.com> MIME-Version: 1.0 References: <1dbad3150703221504u71e3db44sbefeed758ed253db@mail.gmail.com> <20070322230314.257D445047@ptavv.es.net> <1dbad3150703221617g488c3e96t20e552fc41c265a5@mail.gmail.com> <9363AFA5-0DEF-428A-A6D4-E04A4A414F0B@mac.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: FreeBSD Stable Subject: Re: another error with md malloc based fs 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, 23 Mar 2007 00:11:33 -0000 hi Chuck, hi @list me again, behind the scenes, i would take over my Server by an hoster from Linux to FreeBSD on the running system, while the hoster takes money for pressing 2 buttons and put a disk in my Server.......so i create now a mfs based system that can bootet from disk and resides fully in ram. I have tryed out Colin's depenguinator, but it fails...some times now i would do the steps by hand.... thanks cheers michael 2007/3/23, Chuck Swiger : > > On Mar 22, 2007, at 4:17 PM, Michael Schuh wrote: > > i can't understand how malloc can eat all available > > memory, i have 2Gigs of it ;-) > > so it seems to me i know what i doing, if > > i have 1,6 Gigs free Memory, and i say ok get me 750Megs from > > my 1,6 Gigs of free Memory, what was faulty on that???? > > The two choices involve a swap-based RAMdisk, which can use all of > the available physical RAM it needs to, since this memory is > swappable, or a kernel-memory-based RAMdisk, which uses wired-down > memory from within the kernel. > > You shouldn't or can't create huge kernel-based RAMdisks without > expanding the amount of KVM available to the kernel...it's not > reasonable to wire down hundreds of MB or RAM in almost all situations. > > > i hope it gave another way to use such ram-disk without using > > swap or other harddisk based backend....otoh my ram is not fully > > useful > > for me and i must, after twelve years of using freebsd, looking > > back to > > linux, and that i never would, only for using ramdisks.... > > If you wanted to create a 10MB RAMdisk, using kernel-based memory > would be fine. > > For things which are much larger than that, the kernel's global VM > management is using techniques like page-fault frequency heuristics > and will do a better job of keeping active stuff cached in RAM > (regardless of whether the stuff is part of a running process or part > of your RAMdisk filesystem), if you let the kernel manage the > situation than if you try to configure hundreds of MB which can only > be used for a RAMdisk. > > Anyway, if you want to use Linux instead, nobody here is going to try > to persuade you to do otherwise. Have fun, > > -- > -Chuck > > --=20 =3D=3D=3D michael-schuh.net =3D=3D=3D Michael Schuh Preu=DFenstr. 13 66111 Saarbr=FCcken phone: 0681/8319664 mobil: 0177/9738644 @: michael.schuh@gmail.com =3D=3D=3D Ust-ID: DE251072318 =3D=3D=3D