From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754153Ab1AJSVm (ORCPT ); Mon, 10 Jan 2011 13:21:42 -0500 Received: from mail-ey0-f174.google.com ([209.85.215.174]:35090 "EHLO mail-ey0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754030Ab1AJSVj (ORCPT ); Mon, 10 Jan 2011 13:21:39 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=j3LNDaFlOThth4FNfXZWtBRpXYw4BcwYeryAVKYIHdewe1SD/K2c+w9z2EdrjUoi9S 3ziFk1D49N+XAUB4laaQ/tRuR37MyjgBVwt0xRoNoRTDghMfceQCfYE8Dm+2ZtMsU9gb TRNuvYCIXpD79ASBHqWxIzrdd61KTJZCmH6HY= Message-ID: <4D2B4D3D.2030903@gmail.com> Date: Mon, 10 Jan 2011 19:17:33 +0100 From: Marco Stornelli User-Agent: Mozilla/5.0 (X11; U; Linux i686; it; rv:1.9.1.16) Gecko/20101125 SUSE/3.0.11 Thunderbird/3.0.11 MIME-Version: 1.0 To: "Luck, Tony" CC: Pavel Machek , Linux Kernel , Linux Embedded , Linux FS Devel , Tim Bird Subject: Re: [PATCH 01/17] pramfs: documentation References: <4D25AF02.60208@gmail.com> <4D2777FC.6040509@gmail.com> <4D281D65.1070102@gmail.com> <20110110080839.GA16066@atrey.karlin.mff.cuni.cz> <987664A83D2D224EAE907B061CE93D5301940801B2@orsmsx505.amr.corp.intel.com> In-Reply-To: <987664A83D2D224EAE907B061CE93D5301940801B2@orsmsx505.amr.corp.intel.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Il 10/01/2011 18:35, Luck, Tony ha scritto: >> You'd be better running ext2 over special block device, >> it is quite simple. > > Marco, > > You might want to spend some more time answering this question > (it is a particularly good one). What are the reasons to use > pramfs, rather than a ext2 over a mem<->block driver. You covered > some in your part 0 patch (like ext2 wastes time getting optimal > block placement for rotating media). But it might be a good idea > to go back over them here. From my (lightweight) reading of your > code, it looks like the biggest benefit is avoiding duplicating > the data in the pramfs memory region and the VM page cache ... > which is a big deal for your target audience of hand held devices > where memory is a somewhat scarce resource. But you probably > have other goodness in there too. > > -Tony > I can add that you can "place" the fs wherever you want, ext2 not without to build something "special" as Pavel said. Sincerely I don't know what other add. I think documentation, web site information and benchmark say all. You have got a fs that it's simple, it doesn't consume a lot of resources (you can do a fine tuning via N and bpi options for the metadata space for example), better in performance in this "environment", with the memory protection feature when available....other? I could write a piece of code that it turn on your coffee machine at morning, what do you think? :) Marco