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