1 $NetBSD: TODO,v 1.3 2007/07/19 07:48:10 pooka Exp $ 2 3 Document some possible user-visible changes that may take place. 4 For a complete list, please dump my brain and excavate. 5 6 * figure out what do to with struct vattr, maybe introduce some 7 vattr-like puffs-specific structure (translation costs?) instead 8 of direct exposure 9 10 * make puffs_node opaque outside the library 11 12 * make it possible to cache symlink names and getattr results in 13 the kernel ... although I'm not as critically concerned with the 14 kernel caching as I am with userlevel caching 15 16 * try to implement a kernel policy for VOP_ACCESS, it's called 17 very very often - but this requires some kernel caching 18 19 + also try to figure out how to implement it in cases where it's 20 more difficult to do, e.g. how can we know readdir on sshfs will 21 fail without actually trying to read the directory? If we fail 22 readdir itself, it's treated as success 23 24 * implement file system layering .. this will most likely bring 25 massive changes to how the ops vector is handled, for instance. 26 pcc/pu division should stay quite like the way it is now, but 27 maybe there will be layer specific ops. 28 29 * make puffs more like kernel vfs - or make kernel vfs more like puffs 30 31 * decide what to do about setback operations. they kind of violate 32 the transparency of FAF for op handling 33 34 * remove flags parameter to puffs_init and replace with something 35 more generic 36 37 * fix incoming requests to not require memcpy with continuations 38 (not user-visible?) 39 40 * make continuations play with libpthread, lib/36011 (not user-visible?) 41 42 * clean up the request dispatching / continuation code (not user-visible?) 43
Indexes created Sat Sep 20 22:09:52 GMT 2025