From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265440AbTG1Mav (ORCPT ); Mon, 28 Jul 2003 08:30:51 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265652AbTG1Mav (ORCPT ); Mon, 28 Jul 2003 08:30:51 -0400 Received: from nic.bme.hu ([152.66.115.1]:33250 "EHLO nic.bme.hu") by vger.kernel.org with ESMTP id S265440AbTG1Mat (ORCPT ); Mon, 28 Jul 2003 08:30:49 -0400 Message-ID: <3F251A97.9010409@namesys.com> Date: Mon, 28 Jul 2003 16:44:07 +0400 From: Hans Reiser User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030210 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Egger Cc: Nikita Danilov , Linux Kernel Mailinglist , reiserfs mailing list Subject: Re: Reiser4 status: benchmarked vs. V3 (and ext3) References: <3F1EF7DB.2010805@namesys.com> <1059062380.29238.260.camel@sonja> <16160.4704.102110.352311@laputa.namesys.com> <1059093594.29239.314.camel@sonja> <16161.10863.793737.229170@laputa.namesys.com> <1059142851.6962.18.camel@sonja> <3F23CCBC.9070600@namesys.com> <1059315409.10692.215.camel@sonja> In-Reply-To: <1059315409.10692.215.camel@sonja> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Daniel Egger wrote: >Am Son, 2003-07-27 um 14.59 schrieb Hans Reiser: > > > >>I thought that close was fine, it was putting it in the same block that >>was the problem? >> >> > >This looks fine for normal harddrives put on flash you'd probably like >to write the data evenly over the free space in some already formatted >section still leaving the oportunity to format some other sectors to not >run out of space. > I was not able to parse the sentence above.;-) > > > >>Again, I think this is best solved in the device layer. >> >> > >A device layer that shuffles around sectors would have interesting >semantics, like hardly being portable because one would have to use >exactly the same device driver with the same parameters to use the >filesystem and thus retrieve the data. > > > No, you could be more clever than that. -- Hans