Re: ubifs, ubiblk(formatted with vfat) and yaffs2 test.

[Artem Bityutskiy <dedekind@infradead.org>]

On Fri, 2008-05-30 at 15:01 +0900, KeunO Park wrote:
> I am working in embedded device. and I handled some kind of flash
> filesystem like yaffs2, jffs2, rfs on ONENAND/NAND and tffs on MDOC.
> you know, in territory of mobile phone, mass storage class func
> becomes basic function.

Yes, yaffs, jffs2 are "special" class of file-systems and they were not
designed to be what you call "mass storage class func". They should
rather be used as root file system on "internal" flash, which is smaller
than "mass memory", where you store your core libraries, etc. 

> yaffs2
> write: 10.20s, 12.09s, 12.24s avg:11.51s (868KB/s)
> load avg right after copy&sync: 0.03 -> 0.11
> 
> ubifs (LZO)
> write: 14.45s, 14.40s, 14.45s avg:14.43s (693KB/s)
> load avg right after copy&sync: 0.03 -> 0.53
> 
> ubifs (ZLIB)
> write : 27.17s, 27.18s, 27.21s avg:27.18 (367KB/s)
> load avg right after copy&sync: 0.03 -> 0.80
> 
> ubifs (No Compression)
> write: 6.69s, 10.90s, 10.98s avg:9.52s (1050KB/s)
> load avg right after copy&sync: 0.03 -> 0.43
We beat yaffs2? Sounds nice :-)

> ubiblk(vfat mount)
> read: 0.46s, 0.47s, 0.46s avg: 0.463s (21.5MB/s)
> write: 12.13s, 14.95s, 12.61s avg:13.23s (755KB/s)
> load avg right after copy&sync: 0.02 -> 0.31
> 
> With above result, it seems that there is some overload in ubi.
I do not really see what is the question you want to ask.

-- 
Best regards,
Artem Bityutskiy (Битюцкий Артём)