JFFS3 & performance

[Artem B. Bityuckiy]

Jrn Engel wrote:
> Basically, there are two kinds of file attributes.  First the old,
> well-known and well-defined ones from original unix, see stat(2).
> Those are part of the inode for any unix-style filesystem.  Plus any
> arbitraty other attributes, that people may wish for.  Since those are
> neither well-known nor well-defined, we shouldn't statically allocate
> space for them in the inode.
> 
> But I fear that you were talking about something completely different.
> In that case, the "xattr" put me on the wrong track.
I'm aware of xattr basics. Ok, let's put out of mind this for now :-)

> Still not convinced, but I'm too lazy to argue over four bytes.
I think this is not so important now.

I would like create TeX file and put this "JFFS3 checkusm stuff" there. 
This will be "JFFS3 design issues file". It will be accessible via CVS and 
people may  edit it, contributing new ideas.

More questions which I would like to discuss are:

* JFFS3 memory consumption
* JFFS3 & locking

May be:

* mmap "shared" issue
* xattr design

may be other.

After discussing we may put summarized info to that document. Possibly 
this document will be accessible via web as pdf.

Comments?

--
Best Regards,
Artem B. Bityuckiy,
St.-Petersburg, Russia.