From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1045 invoked by alias); 15 Oct 2003 21:02:17 -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 1022 invoked from network); 15 Oct 2003 21:02:16 -0000 Received: from unknown (HELO londo.lunn.ch) (80.238.139.98) by sources.redhat.com with SMTP; 15 Oct 2003 21:02:16 -0000 Received: from lunn by londo.lunn.ch with local (Exim 3.36 #1 (Debian)) id 1A9smd-0007P0-00; Wed, 15 Oct 2003 23:02:15 +0200 Date: Wed, 15 Oct 2003 21:02:00 -0000 To: thomas.koeller@baslerweb.dot.com Cc: eCos Disuss Message-ID: <20031015210215.GC1165@lunn.ch> Mail-Followup-To: thomas.koeller@baslerweb.dot.com, eCos Disuss Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.4i From: Andrew Lunn Subject: [ECOS] Re: Stress testing JFFS2 X-SW-Source: 2003-10/txt/msg00271.txt.bz2 > - Every operation that changes the contents of the FLASH (even > deleting files!) is performed by writing new nodes to the > FLASH. Every such node is represented in RAM by a struct > jffs2_raw_node_ref. The memory occupied by these structs is never > freed unless the file system is unmounted or garbage collection takes > place. If i remember correctly, it think it was once said that the linux version of jffs2 has a thread which does a garbage collect every so often and that eCos does not have such a thread. eCos only does a garbage collect when it really must do. Maybe if you implement the garbage collect thread you can reduce your RAM usage. Andrew -- Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos and search the list archive: http://sources.redhat.com/ml/ecos-discuss