From: Patrick Caulfield <pcaulfie@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] dlm: make lowcomms selectable by user
Date: Fri, 26 Jan 2007 14:40:20 +0000 [thread overview]
Message-ID: <45BA12D4.9040300@redhat.com> (raw)
This patch makes the lowcomms protocol selectable by the user before the DLM is
started rather than having only one available, decided at compile time.
The best way to do this is to have dlm-controld read ccs and write 0 (TCP) or 1
(SCTP) into the sysfs file that controls it.
We will need this when SCTP become a viable protocol for the DLM so that people
can upgrade easily and to give them a sensibly-selectable option without
recompiling the kernel.
The alternative way of doing this would be to have separate modules for tcp &
sctp...I think this solution is better because it is more reliably controlled
via dlm_controld & ccs and this means that all nodes in the cluster will be
using the same transport. The memory overheads of having both loaded at once are
minimal.
Dave/Steve: Can you check this is OK with your criterea (eg is it OK for sysfs,
does Kconfig look right!) for committing it please ?
Signed-Off-By: Patrick Caulfield <pcaulfie@redhat.conm>
--
patrick
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 0001-Make-lowcomms-run-time-ish-switchable.txt
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20070126/4581375c/attachment.txt>
next reply other threads:[~2007-01-26 14:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-26 14:40 Patrick Caulfield [this message]
2007-01-26 15:05 ` [Cluster-devel] [PATCH] [1/2] dlm: make lowcomms selectable by user Patrick Caulfield
2007-01-26 15:05 ` [Cluster-devel] [PATCH] [2/2] " Patrick Caulfield
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45BA12D4.9040300@redhat.com \
--to=pcaulfie@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).