fdda387f73
The following patch adds a TCP based communications layer to the DLM which is compile time selectable. The existing SCTP layer gives the advantage of allowing multihoming, whereas the TCP layer has been heavily tested in previous versions of the DLM and is known to be robust and therefore can be used as a baseline for performance testing. Signed-off-by: Patrick Caulfield <pcaulfie@redhat.com> Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
38 lines
867 B
Plaintext
38 lines
867 B
Plaintext
menu "Distributed Lock Manager"
|
|
depends on INET && IP_SCTP && EXPERIMENTAL
|
|
|
|
config DLM
|
|
tristate "Distributed Lock Manager (DLM)"
|
|
depends on IPV6 || IPV6=n
|
|
select CONFIGFS_FS
|
|
help
|
|
A general purpose distributed lock manager for kernel or userspace
|
|
applications.
|
|
|
|
choice
|
|
prompt "Select DLM communications protocol"
|
|
depends on DLM
|
|
default DLM_TCP
|
|
help
|
|
The DLM Can use TCP or SCTP for it's network communications.
|
|
SCTP supports multi-homed operations whereas TCP doesn't.
|
|
However, SCTP seems to have stability problems at the moment.
|
|
|
|
config DLM_TCP
|
|
bool "TCP/IP"
|
|
|
|
config DLM_SCTP
|
|
bool "SCTP"
|
|
|
|
endchoice
|
|
|
|
config DLM_DEBUG
|
|
bool "DLM debugging"
|
|
depends on DLM
|
|
help
|
|
Under the debugfs mount point, the name of each lockspace will
|
|
appear as a file in the "dlm" directory. The output is the
|
|
list of resource and locks the local node knows about.
|
|
|
|
endmenu
|