Lines Matching full:stack

7  * Glue to the underlying cluster stack.
91  * state for the underlying stack.  ocfs2 does use cc_version to determine
108  * Each cluster stack implements the stack operations structure.  Not used
110  * into stack operations.
115 	 * filesystem to the cluster stack.  The ->connect() op is passed
119 	 * The stack must set up any notification mechanisms and create
136 	 * fs code.  The stack must disengage from the DLM and discontinue
140 	 * be freed.  Thus, a stack must not return from ->disconnect()
143 	 * Once this call returns, the stack glue will be dropping this
160 	 * stack will likely want to wrap ast and bast calls before passing
161 	 * them to stack->sp_proto.  There is no astarg.  The lksb will
176 	 * The unlock ast is not passed, as the stack will want to wrap
177 	 * it before calling stack->sp_proto->lp_unlock_ast().  There is
188 	 * callback pulls out the stack-specific lksb, converts the status
199 	 * Pull the lvb pointer off of the stack-specific lksb.
216 	 * stack can dump debugging information about this lock.
222  * Each stack plugin must describe itself by registering a
224  * stack driver.
250  * Used by callers that don't store their stack name.  They must ensure
251  * all nodes have the same stack.
289 /* Used by stack plugins */