John Dyson 95e5e988e0 Make our v_usecount vnode reference count work identically to the ... original BSD code. The association between the vnode and the vm_object no longer includes reference counts. The major difference is that vm_object's are no longer freed gratuitiously from the vnode, and so once an object is created for the vnode, it will last as long as the vnode does. When a vnode object reference count is incremented, then the underlying vnode reference count is incremented also. The two "objects" are now more intimately related, and so the interactions are now much less complex. When vnodes are now normally placed onto the free queue with an object still attached. The rundown of the object happens at vnode rundown time, and happens with exactly the same filesystem semantics of the original VFS code. There is absolutely no need for vnode_pager_uncache and other travesties like that anymore. A side-effect of these changes is that SMP locking should be much simpler, the I/O copyin/copyout optimizations work, NFS should be more ponderable, and further work on layered filesystems should be less frustrating, because of the totally coherent management of the vnode objects and vnodes. Please be careful with your system while running this code, but I would greatly appreciate feedback as soon a reasonably possible.		1998-01-06 05:26:17 +00:00
..
cd9660
deadfs
fdescfs
fifofs
msdosfs
nullfs
portalfs
procfs	Make our v_usecount vnode reference count work identically to the	1998-01-06 05:26:17 +00:00
specfs	Make our v_usecount vnode reference count work identically to the	1998-01-06 05:26:17 +00:00
umapfs
unionfs