From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22800 invoked by alias); 15 Oct 2003 11:26:28 -0000 Mailing-List: contact ecos-discuss-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@sources.redhat.com Received: (qmail 22792 invoked from network); 15 Oct 2003 11:26:27 -0000 Received: from unknown (HELO proxy.baslerweb.com) (145.253.187.130) by sources.redhat.com with SMTP; 15 Oct 2003 11:26:27 -0000 Received: from comm1.baslerweb.com ([172.16.13.2]) by proxy.baslerweb.com (Post.Office MTA v3.5.3 release 223 ID# 0-0U10L2S100V35) with ESMTP id com; Wed, 15 Oct 2003 13:24:39 +0200 Received: from 172.16.13.253 (VCLINUX-1 [172.16.13.253]) by comm1.baslerweb.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id 32J5G0BW; Wed, 15 Oct 2003 13:26:52 +0200 From: Thomas Koeller Organization: Basler AG To: David Woodhouse Date: Wed, 15 Oct 2003 11:26:00 -0000 User-Agent: KMail/1.5.2 Cc: ecos-discuss@sources.redhat.com, linux-mtd@lists.infradead.org References: <1065598642.12197.6.camel@famine> <200310151211.29172.thomas.koeller@baslerweb.com> <1066215157.14783.933.camel@hades.cambridge.redhat.com> In-Reply-To: <1066215157.14783.933.camel@hades.cambridge.redhat.com> MIME-Version: 1.0 Content-Disposition: inline X-UID: 1241 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200310151330.02902.thomas.koeller@baslerweb.com> Subject: Re: [ECOS] Stress testing JFFS2 X-SW-Source: 2003-10/txt/msg00249.txt.bz2 Hi David, thanks for your quick response. > All correct. But you miss the observation that we also keep a > raw_node_ref around for _obsolete_ nodes, which perhaps we could avoid. > In fact, we do this because the raw_node_ref is in a singly-linked list, > and it's going to be very inefficient to remove obsoleted nodes from > that list when they become obsolete. I do not think this path leads anywhere I want to go. The flash size was chosen to meet the expected storage requirements, which means that at some point the flash will be filled with valid data and consequently there will be few obsoleted nodes. I expect this to be true for most systems. > Omitting the 'totlen' field should be relatively simple if you're not > freeing obsolete refs. Observe that in 99% of cases, it's true that > > ref->totlen == ref_offset(ref->next_phys) - ref_offset(ref) > > Make it 100% and make me believe it, and you can remove totlen from the > structure. > I will consider that. tk -------------------------------------------------- Thomas Koeller, Software Development Basler Vision Technologies An der Strusbek 60-62 22926 Ahrensburg Germany Tel +49 (4102) 463-162 Fax +49 (4102) 463-239 mailto:thomas.koeller@baslerweb.com http://www.baslerweb.com ============================== -- Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos and search the list archive: http://sources.redhat.com/ml/ecos-discuss