mtd/fs/jffs2 TODO,1.9,1.10
David Woodhouse
dwmw2 at infradead.org
Mon Sep 9 12:31:23 EDT 2002
- Previous message: mtd/fs/jffs2 background.c,1.31,1.32 build.c,1.41,1.42 erase.c,1.42,1.43 gc.c,1.84,1.85 nodelist.c,1.61,1.62 nodelist.h,1.83,1.84 nodemgmt.c,1.77,1.78 readinode.c,1.90,1.91 scan.c,1.91,1.92 write.c,1.59,1.60
- Next message: mtd/fs/jffs2 wbuf.c,1.17,1.18
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
Update of /home/cvs/mtd/fs/jffs2
In directory phoenix.infradead.org:/tmp/cvs-serv25527
Modified Files:
TODO
Log Message:
Wheee. TODO update.
Index: TODO
===================================================================
RCS file: /home/cvs/mtd/fs/jffs2/TODO,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- TODO 11 Jul 2002 10:39:04 -0000 1.9
+++ TODO 9 Sep 2002 16:31:21 -0000 1.10
@@ -23,22 +23,18 @@
- Optimisations:
- Stop GC from decompressing and immediately recompressing nodes which could
- just be copied intact.
+ just be copied intact. (We now keep track of REF_PRISTINE flag. Easy now.)
- Furthermore, in the case where it could be copied intact we don't even need
to call iget() for it -- if we use (raw_node_raw->flash_offset & 2) as a flag
to show a node can be copied intact and it's _not_ in icache, we could just do
it, fix up the next_in_ino list and move on. We would need a way to find out
_whether_ it's in icache though -- if it's in icache we also need to do the
fragment lists, etc. P'raps a flag or pointer in the jffs2_inode_cache could
- help.
+ help. (We have half of this now.)
- Stop keeping name in-core with struct jffs2_full_dirent. If we keep the hash in
the full dirent, we only need to go to the flash in lookup() when we think we've
got a match, and in readdir().
- Doubly-linked next_in_ino list to allow us to free obsoleted raw_node_refs immediately?
- Remove totlen from jffs2_raw_node_ref? Need to have totlen passed into
jffs2_mark_node_obsolete(). Can all callers work it out?
- - Don't check data CRC on node scan during mount. We don't really need to know
- yet. This means we can't build up node fragment lists, and hence can't
- build accurate clean/dirty information. But we don't _need_ that for reading,
- only for writing. And in fact we don't even need it for writing until we
- start to need GC.
+ - Remove size from jffs2_raw_node_frag.
- Previous message: mtd/fs/jffs2 background.c,1.31,1.32 build.c,1.41,1.42 erase.c,1.42,1.43 gc.c,1.84,1.85 nodelist.c,1.61,1.62 nodelist.h,1.83,1.84 nodemgmt.c,1.77,1.78 readinode.c,1.90,1.91 scan.c,1.91,1.92 write.c,1.59,1.60
- Next message: mtd/fs/jffs2 wbuf.c,1.17,1.18
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the linux-mtd-cvs
mailing list