blob: c5985b883b2c4f830fd27d1b05aef21e21e8356c [file] [log] [blame]
David Teiglande7fd4172006-01-18 09:30:29 +00001menu "Distributed Lock Manager"
Adrian Bunk1ee48af2006-10-08 04:30:48 +02002 depends on INET && IP_SCTP && EXPERIMENTAL
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
8 help
9 A general purpose distributed lock manager for kernel or userspace
10 applications.
11
Patrick Caulfieldfdda3872006-11-02 11:19:21 -050012choice
13 prompt "Select DLM communications protocol"
14 depends on DLM
15 default DLM_TCP
16 help
17 The DLM Can use TCP or SCTP for it's network communications.
18 SCTP supports multi-homed operations whereas TCP doesn't.
19 However, SCTP seems to have stability problems at the moment.
20
21config DLM_TCP
22 bool "TCP/IP"
23
24config DLM_SCTP
25 bool "SCTP"
26
27endchoice
28
David Teiglande7fd4172006-01-18 09:30:29 +000029config DLM_DEBUG
30 bool "DLM debugging"
31 depends on DLM
32 help
33 Under the debugfs mount point, the name of each lockspace will
34 appear as a file in the "dlm" directory. The output is the
35 list of resource and locks the local node knows about.
36
37endmenu