From manningc2@actrix.gen.nz Tue Mar 09 20:49:17 2010 Received: from smtp.firstline.co.nz ([203.167.210.162] helo=scorch.co.nz) by stoneboat.aleph1.co.uk with smtp (Exim 4.69) (envelope-from ) id 1Np6MX-00076Q-Uh for yaffs@lists.aleph1.co.uk; Tue, 09 Mar 2010 20:49:17 +0000 Received: (qmail 23070 invoked by uid 453); 9 Mar 2010 20:48:57 -0000 X-Virus-Checked: Checked by ClamAV on scorch.co.nz Received: from Unknown (HELO linux-dual-head.local) (10.14.210.25) by scorch.co.nz (qpsmtpd/0.40) with ESMTP; Wed, 10 Mar 2010 09:48:57 +1300 From: Charles Manning To: yaffs@lists.aleph1.co.uk Date: Wed, 10 Mar 2010 09:48:56 +1300 User-Agent: KMail/1.9.10 References: <201003091717.56921.manningc2@actrix.gen.nz> <4B96AB6C.8050104@hasar.com> In-Reply-To: <4B96AB6C.8050104@hasar.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <201003100948.56228.manningc2@actrix.gen.nz> X-SA-Exim-Connect-IP: 203.167.210.162 X-SA-Exim-Mail-From: manningc2@actrix.gen.nz X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on stoneboat.aleph1.co.uk X-Spam-Level: X-Spam-Status: No, score=-1.9 required=4.5 tests=AWL,BAYES_00,SPF_NEUTRAL autolearn=no version=3.2.5 X-SA-Exim-Version: 4.2.1 (built Wed, 25 Jun 2008 17:14:11 +0000) X-SA-Exim-Scanned: Yes (on stoneboat.aleph1.co.uk) Subject: Re: [Yaffs] yaffs background processing: phase 1 X-BeenThere: yaffs@lists.aleph1.co.uk X-Mailman-Version: 2.1.11 Precedence: list List-Id: Discussion of YAFFS NAND flash filesystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Mar 2010 20:49:17 -0000 On Wednesday 10 March 2010 09:11:24 Hugo Etchegoyen wrote: > Charles, > > I've been trying the version with block refreshing and I think it is OK > for static wear-leveling. > > I just want to point out two typos: > > (1) In Kconfig the option YAFFS_DISABLE_BLOCK_REFRESHING is qualified as > "boot" instead of "bool". Thanks. Fixed in cvs. > > (2) In yaffs_fs.c the file /proc/yaffs is created read-only (S_IRUGO | > S_IFREG). Adding S_IWUSR allowed me to configure tracing options by > writing to the file -- very nice! The current permissions allow /proc/yaffs to be written by root. It is bett= er=20 to limit this, IMHO. > > Hugo > > Charles Manning escribi=C3=B3: > > Hi All > > > > I've just added the first phase of background processing to yaffs for > > Linux. > > > > This moves directory updating into the background which reduces the > > amount of writing needed when updating directories. > > > > Phase 2 will move some garbage collection into background too. > > > > -- Charles > > > > > > _______________________________________________ > > yaffs mailing list > > yaffs@lists.aleph1.co.uk > > http://lists.aleph1.co.uk/cgi-bin/mailman/listinfo/yaffs