From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtprelay04.ispgateway.de ([80.67.18.16]) by canuck.infradead.org with esmtp (Exim 4.54 #1 (Red Hat Linux)) id 1EXhrO-0005rp-Rd for linux-mtd@lists.infradead.org; Thu, 03 Nov 2005 11:22:46 -0500 Received: from unknown (HELO deepspace9.in2soft.meep) (547986@[84.153.109.34]) (envelope-sender ) by smtprelay04.ispgateway.de (qmail-ldap-1.03) with SMTP for ; 3 Nov 2005 16:22:36 -0000 Received: from [192.168.0.63] (unknown [192.168.0.63]) by deepspace9.in2soft.meep (Postfix) with ESMTP id 997E0689F for ; Thu, 3 Nov 2005 17:21:34 +0100 (CET) Message-ID: <436A3949.1000001@gmail.com> Date: Thu, 03 Nov 2005 17:22:33 +0100 From: Bernhard Priewasser MIME-Version: 1.0 To: MTD mailing list Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Subject: GC operation List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hello, a question just for better understanding of JFFS2... When and how is GC called? jffs2_garbage_collect_pass() is called from GC thread AND after each writing to flash. But does a single call of jffs2_garbage_collect_pass() (or jffs2_garbage_collect_trigger() or SIGHUP) proceed only one node at a time? For each node / for each block / ..... some loop? Ah, another one: Are blocks on the erase_pending_list erased beside the GC cycles? Hm, sorry for the annoying questions, but garbage collection can be an ugly and confusing thing if one is not used to it :-) Thanks for your assistance! -- Bernhard