Searched refs:hfs_vnop_reclaim (Results 1 - 3 of 3) sorted by relevance

/darwin-on-arm/xnu/bsd/hfs/
H A Dhfs.h601 int hfs_vnop_reclaim(struct vnop_reclaim_args *); /* in hfs_cnode.c */
H A Dhfs_vnops.c4111 * with a call to vnode_recycle. hfs_vnop_reclaim has been modified so that it
5979 { &vnop_reclaim_desc, (VOPFUNC)hfs_vnop_reclaim }, /* reclaim */
6041 { &vnop_reclaim_desc, (VOPFUNC)hfs_vnop_reclaim }, /* reclaim */
6102 { &vnop_reclaim_desc, (VOPFUNC)hfs_vnop_reclaim }, /* reclaim */
6145 { &vnop_reclaim_desc, (VOPFUNC)hfs_vnop_reclaim }, /* reclaim */
H A Dhfs_cnode.c149 * and hfs_vnop_reclaim. As VNOP_INACTIVE is not necessarily called from vnodes
160 * This function is idempotent and safe to call from both hfs_vnop_inactive and hfs_vnop_reclaim
167 * in hfs_vnop_reclaim. hfs_update, by definition, is not necessary if the cnode's catalog
170 * 'reclaim' argument specifies whether or not we were called from hfs_vnop_reclaim. If we are
171 * invoked from hfs_vnop_reclaim, we can not call functions that cluster_push since the UBC info
835 hfs_vnop_reclaim(struct vnop_reclaim_args *ap) function
895 panic("hfs_vnop_reclaim: vp points to wrong cnode (vp=%p cp->c_vp=%p cp->c_rsrc_vp=%p)\n", vp, cp->c_vp, cp->c_rsrc_vp);
1257 * hfs_vnop_reclaim... vnode_get can be called here
1420 * We only call this function if we are in hfs_vnop_reclaim and
1425 * function hfs_vnop_reclaim) i
[all...]

Completed in 49 milliseconds