From mboxrd@z Thu Jan  1 00:00:00 1970
Return-path: <owner-mtd@infradead.org>
Received: from majordomo by infradead.org with local (Exim 3.16 #2)
	id 13rPrC-0005cV-00
	for mtd-list@infradead.org; Thu, 02 Nov 2000 19:17:02 +0000
Received: from dawnmail.dawning.com ([24.93.23.251])
	by infradead.org with esmtp (Exim 3.16 #2)
	id 13rPr9-0005cO-00
	for mtd@infradead.org; Thu, 02 Nov 2000 19:17:01 +0000
Received: from [192.168.0.142] by dawnmail.dawning.com (NTMail 4.30.0013/NY3896.00.832c5e1f) with ESMTP id bdsfaaaa for <mtd@infradead.org>; Thu, 2 Nov 2000 14:17:55 -0500
Message-ID: <3A01BDA9.52756588@dawning.com>
Date: Thu, 02 Nov 2000 14:16:57 -0500
From: Gregory Schallert <gschallert@dawning.com>
MIME-Version: 1.0
To: mark.langsdorf@amd.com
CC: mtd@infradead.org
Subject: Re: Problems with AMD CFI chips
References: <0FA1031B65A9D111960900805F9FA8E103B9F19F@txexmta8.amd.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mtd@infradead.org
List-ID: <linux-mtd.lists.infradead.org>

>    Also, when does jffs attempt to clean out the dirty
> space?

On an aside, how does jffs schedule the clean up and is this really CPU
intensive?



To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org