Lines Matching full:stack

5  * Glue to the underlying cluster stack.
89  * state for the underlying stack.  ocfs2 does use cc_version to determine
106  * Each cluster stack implements the stack operations structure.  Not used
108  * into stack operations.
113 	 * filesystem to the cluster stack.  The ->connect() op is passed
117 	 * The stack must set up any notification mechanisms and create
134 	 * fs code.  The stack must disengage from the DLM and discontinue
138 	 * be freed.  Thus, a stack must not return from ->disconnect()
141 	 * Once this call returns, the stack glue will be dropping this
158 	 * stack will likely want to wrap ast and bast calls before passing
159 	 * them to stack->sp_proto.  There is no astarg.  The lksb will
174 	 * The unlock ast is not passed, as the stack will want to wrap
175 	 * it before calling stack->sp_proto->lp_unlock_ast().  There is
186 	 * callback pulls out the stack-specific lksb, converts the status
197 	 * Pull the lvb pointer off of the stack-specific lksb.
214 	 * stack can dump debugging information about this lock.
220  * Each stack plugin must describe itself by registering a
222  * stack driver.
248  * Used by callers that don't store their stack name.  They must ensure
249  * all nodes have the same stack.
287 /* Used by stack plugins */