Hi, <div>   Regarding the partial page write programming, I do not believe it is possible because the write cannot take place in-place on disk. YAFFS2 can write each chunk only once on disk before the whole block gets erased. You can only write in-place as long as the chunk is in main memory. For small writes the efficiency of data storage will be low, I believe.<br>
<br><div class="gmail_quote">On Sat, Oct 13, 2012 at 3:47 PM, 姚乾 <span dir="ltr">&lt;<a href="mailto:andrewyauq@gmail.com" target="_blank">andrewyauq@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>Hi everyone,<br>I’m doing a research recently about water conservancy informatization. The monitoring terminal is using ‘linux + yaffs’ system. Since the rainfall information collected each time is only 20 bytes, yaffs file system usually applies the ‘out of place’ strategy. I don’t think this is quite an efficient way. So how about adding ‘partial page programming’ into yaffs which directly stores new data following the original without assigning new chunk while small data file is being written.<br>

I’m wondering if partial page programming can meet the accuracy and reliability of data storage? Or better solutions to deal with small data storage would be a great help. I’m open to any kind of suggestion. <br>Thanks a lot! </div>

<br>_______________________________________________<br>
yaffs mailing list<br>
<a href="mailto:yaffs@lists.aleph1.co.uk">yaffs@lists.aleph1.co.uk</a><br>
<a href="http://lists.aleph1.co.uk/cgi-bin/mailman/listinfo/yaffs" target="_blank">http://lists.aleph1.co.uk/cgi-bin/mailman/listinfo/yaffs</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br>Regards,<br>Ravi Tandon.<br><div><br></div><div><br></div><br>
</div>