blob: b5654a284fef1283b1186d7e39dcc1e0b3426396 [file] [log] [blame]
David Teiglande7fd4172006-01-18 09:30:29 +00001menu "Distributed Lock Manager"
Patrick Caulfieldb98c95a2006-11-15 12:29:24 -05002 depends on EXPERIMENTAL && INET
David Teiglande7fd4172006-01-18 09:30:29 +00003
4config DLM
5 tristate "Distributed Lock Manager (DLM)"
David Teiglande7fd4172006-01-18 09:30:29 +00006 depends on IPV6 || IPV6=n
David Teiglande7fd4172006-01-18 09:30:29 +00007 select CONFIGFS_FS
Patrick Caulfieldb98c95a2006-11-15 12:29:24 -05008 select IP_SCTP if DLM_SCTP
David Teiglande7fd4172006-01-18 09:30:29 +00009 help
10 A general purpose distributed lock manager for kernel or userspace
11 applications.
12
Patrick Caulfieldfdda3872006-11-02 11:19:21 -050013choice
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
David Teiglande7fd4172006-01-18 09:30:29 +000030config DLM_DEBUG
31 bool "DLM debugging"
32 depends on DLM
33 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.
37
38endmenu