From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6960 invoked by alias); 13 Jul 2004 07:53:21 -0000 Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Received: (qmail 6951 invoked from network); 13 Jul 2004 07:53:20 -0000 Received: from unknown (HELO londo.lunn.ch) (80.238.139.98) by sourceware.org with SMTP; 13 Jul 2004 07:53:20 -0000 Received: from lunn by londo.lunn.ch with local (Exim 3.36 #1 (Debian)) id 1BkI6I-0002gt-00; Tue, 13 Jul 2004 09:53:18 +0200 Date: Tue, 13 Jul 2004 07:53:00 -0000 To: ?yvind Harboe , ecos-discuss@sources.redhat.com Message-ID: <20040713075318.GP18802@lunn.ch> Mail-Followup-To: ?yvind Harboe , ecos-discuss@sources.redhat.com References: <1089643331.3951.42.camel@famine> <20040713074052.GO18802@lunn.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040713074052.GO18802@lunn.ch> User-Agent: Mutt/1.5.6+20040523i From: Andrew Lunn Subject: Re: [ECOS] JFFS2 eats memory X-SW-Source: 2004-07/txt/msg00167.txt.bz2 > > Presumably when the raw nodes in the file fragement list are marked as > > obsolete, they are no longer required, but are not freed. One other thing. You might consider try gettting the garbage collect code runnig. This might help solve your problem. I guess as a proof of concept just call jffs2_garbage_collect_pass(JFFS2_SB_INFO(jffs2_sb)); This is not strictly correct since you need to add locking to one of the lists to make this thread safe. I forget which and i've forgotten where i read about this, but im sure google will find it for you. Andrew -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss