From: Aditya Kashyap Subject: Re: single-file file system? (fwd) Date: Fri, 1 Oct 2004 00:21:22 -0400 (EDT) Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: References: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: linux-fsdevel Return-path: Received: from sbcs.sunysb.edu ([130.245.1.15]:39880 "EHLO sbcs.cs.sunysb.edu") by vger.kernel.org with ESMTP id S269688AbUJAEY5 (ORCPT ); Fri, 1 Oct 2004 00:24:57 -0400 To: Andi Kleen In-Reply-To: List-Id: linux-fsdevel.vger.kernel.org Hello all, > iirc there was one long ago from Miquel van Smoorenburg for 2.4 (or maybe > 2.2 i don't remember). But if you want it for 2.6 it would be probably > easier to just rewrite it. > > -Andi I found the file system that Andi Kleen talked about: rawfs, written by Miquel van Smoorenburg. It was last tested on 2.4.20, and abstracts a disk partition as a single file in a simple mountable file system. I ran a benchmark on both, the file exported by rawfs, and the raw disk, which I shall proceed to describe. The benchmark opens the file passed to it, randomly seeks to a position in the file, and randomly chooses to either read or write a 4k block from or to the file. The mean times from both the experiments are as follows. What is being shown is the time taken for the process to run on the file exported by rawfs, and the raw disk partition. Both the experiments were run enough times to reduce standard deviation to a minimum. -> RAWFS exporting a 2GB partition: Time MEAN (sec) ---- ---------- Elapsed 66.9925 User 0.0370 System 0.2510 I/O 66.7045 -> Plain 2GB partition (/dev/hdXY): Time MEAN (sec) ---- ---------- Elapsed 74.1280 User 0.0330 System 0.2990 I/O 73.7960 The numbers above show a 10% overhead in I/O time for the plain partition over rawfs. My question is, I wonder how rawfs performs better on the benchmark over directly accessing the raw partition, when both of them have very similar operations when reading or writing data. Any ideas on how this could be? Thanks, Aditya