Kconfig (5a84d159061d914c8dd4aa372ac6e9529c2be453) | Kconfig (6ed7257b46709e87d79ac2b6b819b7e0c9184998) |
---|---|
1menu "Distributed Lock Manager" 2 depends on EXPERIMENTAL && INET 3 4config DLM 5 tristate "Distributed Lock Manager (DLM)" | 1menu "Distributed Lock Manager" 2 depends on EXPERIMENTAL && INET 3 4config DLM 5 tristate "Distributed Lock Manager (DLM)" |
6 depends on SYSFS && (IPV6 || IPV6=n) | 6 depends on IPV6 || IPV6=n |
7 select CONFIGFS_FS | 7 select CONFIGFS_FS |
8 select IP_SCTP if DLM_SCTP | 8 select IP_SCTP |
9 help | 9 help |
10 A general purpose distributed lock manager for kernel or userspace 11 applications. | 10 A general purpose distributed lock manager for kernel or userspace 11 applications. |
12 | 12 |
13choice 14 prompt "Select DLM communications protocol" 15 depends on DLM 16 default DLM_TCP 17 help 18 The DLM Can use TCP or SCTP for it's network communications. 19 SCTP supports multi-homed operations whereas TCP doesn't. 20 However, SCTP seems to have stability problems at the moment. 21 22config DLM_TCP 23 bool "TCP/IP" 24 25config DLM_SCTP 26 bool "SCTP" 27 28endchoice 29 | |
30config DLM_DEBUG 31 bool "DLM debugging" 32 depends on DLM 33 help | 13config DLM_DEBUG 14 bool "DLM debugging" 15 depends on DLM 16 help |
34 Under the debugfs mount point, the name of each lockspace will 35 appear as a file in the "dlm" directory. The output is the 36 list of resource and locks the local node knows about. | 17 Under the debugfs mount point, the name of each lockspace will 18 appear as a file in the "dlm" directory. The output is the 19 list of resource and locks the local node knows about. |
37 38endmenu | 20 21endmenu |