aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMateusz Guzik <mjg@FreeBSD.org>2021-09-18 08:14:35 +0000
committerMateusz Guzik <mjg@FreeBSD.org>2021-09-18 10:16:00 +0000
commit5d8e32a66c1700323c570d25b03672f35f4e0110 (patch)
treee41f6404da60b15004a9247b5a6b6c93d64911e4
parent007c2463d6d017ad5321d5cd2bc500e577d22196 (diff)
downloadsrc-5d8e32a66c1700323c570d25b03672f35f4e0110.tar.gz
src-5d8e32a66c1700323c570d25b03672f35f4e0110.zip
vfs: retire VNODE_REFCOUNT_FENCE_* macros
They are unused as of last year.
-rw-r--r--sys/kern/vfs_subr.c16
1 files changed, 0 insertions, 16 deletions
diff --git a/sys/kern/vfs_subr.c b/sys/kern/vfs_subr.c
index 23f6ec9cf3fd..33a556fbfa2b 100644
--- a/sys/kern/vfs_subr.c
+++ b/sys/kern/vfs_subr.c
@@ -122,22 +122,6 @@ static int v_inval_buf_range_locked(struct vnode *vp, struct bufobj *bo,
static void vnlru_recalc(void);
/*
- * These fences are intended for cases where some synchronization is
- * needed between access of v_iflags and lockless vnode refcount (v_holdcnt
- * and v_usecount) updates. Access to v_iflags is generally synchronized
- * by the interlock, but we have some internal assertions that check vnode
- * flags without acquiring the lock. Thus, these fences are INVARIANTS-only
- * for now.
- */
-#ifdef INVARIANTS
-#define VNODE_REFCOUNT_FENCE_ACQ() atomic_thread_fence_acq()
-#define VNODE_REFCOUNT_FENCE_REL() atomic_thread_fence_rel()
-#else
-#define VNODE_REFCOUNT_FENCE_ACQ()
-#define VNODE_REFCOUNT_FENCE_REL()
-#endif
-
-/*
* Number of vnodes in existence. Increased whenever getnewvnode()
* allocates a new vnode, decreased in vdropl() for VIRF_DOOMED vnode.
*/