Next: About this document ...
Up: JFFS3 design issues
Previous: Credits
Contents
This section contains the gathered list of different ideas and thoughts
suggested by different people but have not yet highlighted/used in this
document. Many of them may be quite useful.
- Make the compression selectable per-file (may be using xattr).
http://lists.infradead.org/pipermail/linux-mtd/2005-January/011645.html.
- Make one more checksum mode when checksums are neither
generated nor checked.
http://lists.infradead.org/pipermail/linux-mtd/2005-January/011640.html.
- Have special type of nodes where we may store static inode node's
(and may be other's) attributes like UID and GID. Perhaps, the xattr
support may be used here.
http://lists.infradead.org/pipermail/linux-mtd/2005-January/011615.html.
- Implement xattr support. There are a lot of cases when having it
would be very handy.
http://lists.infradead.org/pipermail/linux-mtd/2005-January/011617.html
http://lists.infradead.org/pipermail/linux-mtd/2005-January/011632.html
http://lists.infradead.org/pipermail/linux-mtd/2005-January/011644.html
http://lists.infradead.org/pipermail/linux-mtd/2005-January/011556.html
- Make compression selectable per file.
http://lists.infradead.org/pipermail/linux-mtd/2005-January/011641.html
- Have the end magic bitmask on all note types in order to be able
to quickly detect the partially written nodes.
http://lists.infradead.org/pipermail/linux-mtd/2005-January/011529.html.
- Increase the maximum node size. We may keep several pages in one node.
This leads to better compression and less memory consumption. Use
zisofs-like technique when reading the node with several pages of data
(compressed).
http://lists.infradead.org/pipermail/linux-mtd/2005-January/011672.html
and following.
- Implement write-back cache in JFFS3.
http://lists.infradead.org/pipermail/linux-mtd/2005-January/011672.html
and following.
Next: About this document ...
Up: JFFS3 design issues
Previous: Credits
Contents
2005-04-23