summaryrefslogtreecommitdiffstats
path: root/usr.bin/rup
diff options
context:
space:
mode:
authorbp <bp@FreeBSD.org>2000-09-25 15:24:04 +0000
committerbp <bp@FreeBSD.org>2000-09-25 15:24:04 +0000
commit6110b03d2438de0cb3f47dbce3cec5c1dfa712f6 (patch)
tree104536559087d506b1c196e2562f5ecc57690734 /usr.bin/rup
parent520f10057961f03f20c2b980adff11bbfa8c2d6d (diff)
downloadFreeBSD-src-6110b03d2438de0cb3f47dbce3cec5c1dfa712f6.zip
FreeBSD-src-6110b03d2438de0cb3f47dbce3cec5c1dfa712f6.tar.gz
Add a lock structure to vnode structure. Previously it was either allocated
separately (nfs, cd9660 etc) or keept as a first element of structure referenced by v_data pointer(ffs). Such organization leads to known problems with stacked filesystems. From this point vop_no*lock*() functions maintain only interlock lock. vop_std*lock*() functions maintain built-in v_lock structure using lockmgr(). vop_sharedlock() is compatible with vop_stdunlock(), but maintains a shared lock on vnode. If filesystem wishes to export lockmgr compatible lock, it can put an address of this lock to v_vnlock field. This indicates that the upper filesystem can take advantage of it and use single lock structure for entire (or part) of stack of vnodes. This field shouldn't be examined or modified by VFS code except for initialization purposes. Reviewed in general by: mckusick
Diffstat (limited to 'usr.bin/rup')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud