[lkml]   [2008]   [Mar]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subject[PATCH 0/18] ocfs2: Cluster stack glue layer
ocfs2 is currently tied to its internal cluster stack, the ocfs2 Cluster
Base (o2cb). This includes the nodemanager (o2nm) and distributed lock
manager (o2dlm).

Going forward, ocfs2 would like to use the DLM in fs/dlm. This includes
interacting with userspace cluster stacks that drive fs/dlm, allowing
all clustering on a machine to use the same stack.

This patch series decouples the o2cb stack from ocfs2, creating a
plug-in architecture. A layer called "stackglue" sits between the ocfs2
filesystem and the chosen cluster plug-in. A later patch series will
introduce the plug-in for fs/dlm and userspace cluster stacks.

The series should be functionally equivalent. Each patch should compile
and run successfully, with no modification to userspace tools. The end
result of this series is a plug-in cluster backend that behaves exactly
as the current system does. As an added benefit, local (non-clustered)
ocfs2 filesystems do not need to load any plug-in. In the past, even a
non-clustered filesystem required the o2cb modules loaded, though not

The kernel code is also available on the 'stack-glue' branch of my git

git pull git:// stack-glue

 \ /
  Last update: 2008-03-06 01:31    [W:0.266 / U:1.768 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site