From owner-freebsd-arm@FreeBSD.ORG Mon Mar 3 06:15:29 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D7530C89 for ; Mon, 3 Mar 2014 06:15:29 +0000 (UTC) Received: from mail-ig0-f170.google.com (mail-ig0-f170.google.com [209.85.213.170]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9FEB2D2A for ; Mon, 3 Mar 2014 06:15:29 +0000 (UTC) Received: by mail-ig0-f170.google.com with SMTP id uq10so1260027igb.1 for ; Sun, 02 Mar 2014 22:15:23 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=Qhlr/7a4OKIUY8OFACJpUTg+YNYuJLrFX/sI0gZ29fg=; b=DLtiw6MiggBpUfIUAt4xj/BpDgbfWMAkoymbYL2IakksdRai5gh0XkPsVj5CiJKUxo l8uAP6G6ArR7HDT7iYvGM4u2FYvjI3HeBOlii4tb8F9nKf9C+r1wd7qh9Tupq2VMmhhg jr2lUxX2OQXmHQo4rCFVSGJ5HPLXmPk8PLb9tFfuScoRDVERYzRtCXhNZ7lo6EZODeB0 zpQzP2jxOuiofXVvFYkgJLSsIsJpgZ0XhvYB29k5lELsvTi4qMmqvmKbPmDVWSXlA54U IbFI+CPpDbIxRvuyEN+6PW+e/xVd3hezWLsv5dbEZXVp88gfjbQSdURw0YkWbUN8GNxs fYGg== X-Gm-Message-State: ALoCoQm7Ypq5EKBtWb3Ykp7Ue0/f1FcKYLbTt3lDVF+chB20EGKM0jrTarn3j2n9kBKC11mfjpMo X-Received: by 10.42.232.206 with SMTP id jv14mr24111704icb.52.1393827323444; Sun, 02 Mar 2014 22:15:23 -0800 (PST) Received: from netflix-mac.bsdimp.com (50-78-194-198-static.hfc.comcastbusiness.net. [50.78.194.198]) by mx.google.com with ESMTPSA id ai4sm36236783igd.3.2014.03.02.22.15.22 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 02 Mar 2014 22:15:23 -0800 (PST) Sender: Warner Losh Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) Subject: Re: TMPFS in kernels From: Warner Losh In-Reply-To: <20140303061136.GB85204@zibbi.meraka.csir.co.za> Date: Sun, 2 Mar 2014 23:15:24 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <595B99F0-264D-41D3-9151-FFCFD0261AFD@bsdimp.com> References: <5313D0FE.8010008@ceetonetechnology.com> <1393818974.1149.270.camel@revolution.hippie.lan> <5314016B.1000107@ceetonetechnology.com> <20140303061136.GB85204@zibbi.meraka.csir.co.za> To: John Hay X-Mailer: Apple Mail (2.1874) Cc: George Rosamond , freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Mar 2014 06:15:29 -0000 On Mar 2, 2014, at 11:11 PM, John Hay wrote: > On Sun, Mar 02, 2014 at 11:13:31PM -0500, George Rosamond wrote: >> Ian Lepore: >>> On Sun, 2014-03-02 at 19:46 -0500, George Rosamond wrote: >>>> Is there a reason why TMPFS(5) is not in the 10-Stable's ALIX and = RPI-B >>>> kernels, yet in BEAGLEBONE? Haven't checked the others. >>>>=20 >>>> Seems like a strong and mature replacement for md(4) from my >>>> experiences, and probably belongs in the Crochet fstabs. I have = been >>>> using on Alix, RPis, x86 for a long while, and never had any >>>> (noticeable) issues. >>>>=20 >>>> g >>>=20 >>> I agree. Should we add it to all configs, or just to armv6 configs? >>>=20 >>=20 >> I'd assume we should have it all the kernels.. especially since most = of >> them are running off flash-type media, which makes memory-based disks >> pretty vital. >=20 > Our embedded systems also use compact flash disks mounted ro. We have > been (ab)using the nice etc/rc.initdiskless and etc/rc.d/var scripts > by just having an etc/diskless and populated conf/base and = conf/defaults > directories. But it seems those scripts just work with md devices. NANOBSD works that way too=85 tmpfs is a bit nicer since it doesn=92t = hard-wire the allocation, but that can suffer a bit from the vagaries of system demand=85. Warner