1*e7fd4179SDavid Teiglandmenu "Distributed Lock Manager" 2*e7fd4179SDavid Teigland depends on INET && EXPERIMENTAL 3*e7fd4179SDavid Teigland 4*e7fd4179SDavid Teiglandconfig DLM 5*e7fd4179SDavid Teigland tristate "Distributed Lock Manager (DLM)" 6*e7fd4179SDavid Teigland depends on SYSFS 7*e7fd4179SDavid Teigland depends on IPV6 || IPV6=n 8*e7fd4179SDavid Teigland select IP_SCTP 9*e7fd4179SDavid Teigland select CONFIGFS_FS 10*e7fd4179SDavid Teigland help 11*e7fd4179SDavid Teigland A general purpose distributed lock manager for kernel or userspace 12*e7fd4179SDavid Teigland applications. 13*e7fd4179SDavid Teigland 14*e7fd4179SDavid Teiglandconfig DLM_DEVICE 15*e7fd4179SDavid Teigland tristate "DLM device for userspace access" 16*e7fd4179SDavid Teigland depends on DLM 17*e7fd4179SDavid Teigland help 18*e7fd4179SDavid Teigland This module creates a misc device through which the dlm lockspace 19*e7fd4179SDavid Teigland and locking functions become available to userspace applications 20*e7fd4179SDavid Teigland (usually through the libdlm library). 21*e7fd4179SDavid Teigland 22*e7fd4179SDavid Teiglandconfig DLM_DEBUG 23*e7fd4179SDavid Teigland bool "DLM debugging" 24*e7fd4179SDavid Teigland depends on DLM 25*e7fd4179SDavid Teigland help 26*e7fd4179SDavid Teigland Under the debugfs mount point, the name of each lockspace will 27*e7fd4179SDavid Teigland appear as a file in the "dlm" directory. The output is the 28*e7fd4179SDavid Teigland list of resource and locks the local node knows about. 29*e7fd4179SDavid Teigland 30*e7fd4179SDavid Teiglandendmenu 31