From hetchegoyen@hasar.com Tue Mar 09 20:07:03 2010 Received: from mail.hasar.com ([200.80.204.3] helo=mx1.hasar.com) by stoneboat.aleph1.co.uk with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1Np5hg-0005Px-Ts for yaffs@lists.aleph1.co.uk; Tue, 09 Mar 2010 20:07:03 +0000 X-HASAR-MailScanner-Watermark: 1268770007.98623@J4npsKu2WPJ3foP+WS6hXA Received: from mailserver.hasar.com (mailserver.hasar [192.168.1.80]) by mx1.hasar.com (8.14.2/8.14.2/ATDT) with ESMTP id o29K6ksj023466 for ; Tue, 9 Mar 2010 18:06:47 -0200 Received: (qmail 26651 invoked from network); 9 Mar 2010 20:03:49 -0000 Received: from unknown (HELO [192.0.2.142]) ([192.0.2.142]) (envelope-sender ) by 0 (qmail-ldap-1.03) with SMTP for ; 9 Mar 2010 20:03:49 -0000 Message-ID: <4B96AB6C.8050104@hasar.com> Date: Tue, 09 Mar 2010 17:11:24 -0300 From: Hugo Etchegoyen User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: yaffs@lists.aleph1.co.uk References: <201003091717.56921.manningc2@actrix.gen.nz> In-Reply-To: <201003091717.56921.manningc2@actrix.gen.nz> Content-Type: multipart/alternative; boundary="------------010403040108020603010804" X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.3 (mx1.hasar.com [192.168.1.77]); Tue, 09 Mar 2010 18:06:47 -0200 (ARST) X-HASAR-MailScanner-Information: Please contact the ISP for more information X-HASAR-MailScanner-ID: o29K6ksj023466 X-HASAR-MailScanner: Found to be clean X-HASAR-MailScanner-From: hetchegoyen@hasar.com X-SA-Exim-Connect-IP: 200.80.204.3 X-SA-Exim-Mail-From: hetchegoyen@hasar.com 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_05,HTML_MESSAGE 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:07:03 -0000 This is a multi-part message in MIME format. --------------010403040108020603010804 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by mx1.hasar.com id o29K6ksj023466 Charles, I've been trying the version with block refreshing and I think it is OK=20 for static wear-leveling. I just want to point out two typos: (1) In Kconfig the option YAFFS_DISABLE_BLOCK_REFRESHING is qualified as=20 "boot" instead of "bool". (2) In yaffs_fs.c the file /proc/yaffs is created read-only (S_IRUGO |=20 S_IFREG). Adding S_IWUSR allowed me to configure tracing options by=20 writing to the file -- very nice! Hugo Charles Manning escribi=F3: > Hi All > > I've just added the first phase of background processing to yaffs for L= inux. > > This moves directory updating into the background which reduces the amo= unt of=20 > writing needed when updating directories. > > Phase 2 will move some garbage collection into background too. > > -- Charles > =20 > > _______________________________________________ > yaffs mailing list > yaffs@lists.aleph1.co.uk > http://lists.aleph1.co.uk/cgi-bin/mailman/listinfo/yaffs > > > =20 --=20 Ing. Hugo Eduardo Etchegoyen* *Gerente Dto. Software de Base Compa=F1=EDa Hasar | Grupo Hasar* *Marcos Sastre y Jos=E9 Ingenieros El Talar. Pacheco [B1618CSD] Buenos Aires. Argentina Tel [54 11] 4117 8900 | Fax [54 11] 4117 8998 E-mail: hetchegoyen@hasar.com Vis=EDtenos en: www.hasar.com Informaci=F3n legal y pol=EDtica de confidencialida= d:=20 www.grupohasar.com/disclaimer --------------010403040108020603010804 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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".

(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!

Hugo

Charles Manning escribió: 
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

--
Grupo Hasar

Ing. Hugo Eduardo Etchegoyen
Gerente Dto. Software de Base

Compañía Hasar | Grupo Hasar
Marcos Sastre y José Ingenieros
El Talar. Pacheco
[B1618CSD] Buenos Aires. Argentina
Tel [54 11] 4117 8900 | Fax [54 11] 4117 8998
E-mail: hetchegoyen@hasar.com
Visítenos en: www.hasar.com
Información legal y política de confidencialidad: www.grupohasar.com/disclaimer

--------------010403040108020603010804--