From: "Gang He" <ghe@suse.com>
To: <teigland@redhat.com>, "Gang He" <GHe@suse.com>
Cc: <cluster-devel@redhat.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] dlm: prompt the user SCTP is experimental
Date: Thu, 22 Mar 2018 22:27:56 -0600 [thread overview]
Message-ID: <5AB4F2CC020000F9000B145C@prv-mh.provo.novell.com> (raw)
In-Reply-To: <1521528327-882-1-git-send-email-ghe@suse.com>
Hello David,
Do you agree to add this prompt to the user?
Since sometimes customers attempted to setup SCTP protocol with two rings,
but they could not get the expected result, then it maybe bring some concerns to the customer for DLM qualities.
Thanks
Gang
>>>
> As you know, DLM module can use TCP or SCTP protocols to
> communicate among the cluster.
> But, according to our testing, SCTP protocol is still considered
> experimental, since not all aspects are working correctly and
> it is not full tested.
> e.g. SCTP connection channel switch needs about 5mins hang in case
> one connection(ring) is broken.
> Then, I suggest to add a kernel print, which prompts the user SCTP
> protocol for DLM should be considered experimental, it is not
> recommended in production environment.
>
> Signed-off-by: Gang He <ghe@suse.com>
> ---
> fs/dlm/lowcomms.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/fs/dlm/lowcomms.c b/fs/dlm/lowcomms.c
> index cff79ea..18fd85d 100644
> --- a/fs/dlm/lowcomms.c
> +++ b/fs/dlm/lowcomms.c
> @@ -1307,6 +1307,7 @@ static int sctp_listen_for_all(void)
> return -ENOMEM;
>
> log_print("Using SCTP for communications");
> + log_print("SCTP protocol is experimental, use at your own risk");
>
> result = sock_create_kern(&init_net, dlm_local_addr[0]->ss_family,
> SOCK_STREAM, IPPROTO_SCTP, &sock);
> --
> 1.8.5.6
next prev parent reply other threads:[~2018-03-23 4:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 6:45 Gang He
2018-03-23 4:27 ` Gang He [this message]
2018-04-02 15:03 ` David Teigland
2018-04-03 2:01 ` Gang He
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=5AB4F2CC020000F9000B145C@prv-mh.provo.novell.com \
--to=ghe@suse.com \
--cc=cluster-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=teigland@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
all inboxes | Powered by JetHome®