From: Heming Zhao <heming.zhao@suse.com>
To: teigland@redhat.com, aahringo@redhat.com
Cc: Heming Zhao <heming.zhao@suse.com>,
ccaulfie@redhat.com, jfriesse@redhat.com, nicholas.yang@suse.com,
glass.su@suse.com, gfs2@lists.linux.dev
Subject: [PATCH] dlm_controld: Support for extended value of kernel
Date: Fri, 21 Feb 2025 23:06:07 +0800 [thread overview]
Message-ID: <20250221150611.21167-1-heming.zhao@suse.com> (raw)
This patch should work with the updated kernel dlm module, because
the code changes need to be aligned with the DLM_MAX_ADDR_COUNT value.
Another notice is that with the current dlm_controld code, users
should explicitly add 'protocol=sctp' to the dlm.conf in a corosync
3.x env.
Signed-off-by: Heming Zhao <heming.zhao@suse.com>
---
dlm_controld/dlm_daemon.h | 6 +++---
dlm_sand/sand_internal.h | 4 ++--
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/dlm_controld/dlm_daemon.h b/dlm_controld/dlm_daemon.h
index 4a533e3451e2..c902228f890f 100644
--- a/dlm_controld/dlm_daemon.h
+++ b/dlm_controld/dlm_daemon.h
@@ -175,10 +175,10 @@ EXTERN struct dlm_option dlm_options[dlm_options_max];
#define MAX_NODES 128
-/* Maximum number of IP addresses per node, when using SCTP and multi-ring in
- corosync In dlm-kernel this is DLM_MAX_ADDR_COUNT, currently 3. */
+/* Maximum number of IP addresses per node, when using SCTP and multi-[ring|link]
+ in corosync [2|3]. In dlm-kernel this is DLM_MAX_ADDR_COUNT, currently 8. */
-#define MAX_NODE_ADDRESSES 4
+#define MAX_NODE_ADDRESSES 8
#define PROTO_TCP 0
#define PROTO_SCTP 1
diff --git a/dlm_sand/sand_internal.h b/dlm_sand/sand_internal.h
index 4c2fc0897051..c17287abcd47 100644
--- a/dlm_sand/sand_internal.h
+++ b/dlm_sand/sand_internal.h
@@ -138,9 +138,9 @@ EXTERN struct dlm_option dlm_options[dlm_options_max];
Copied in libdlm.h so apps don't need to include the kernel header. */
/* Maximum number of IP addresses per node, when using SCTP.
- In dlm-kernel this is DLM_MAX_ADDR_COUNT, currently 3. */
+ In dlm-kernel this is DLM_MAX_ADDR_COUNT, currently 8. */
-#define MAX_NODE_ADDRESSES 4
+#define MAX_NODE_ADDRESSES 8
#define PROTO_TCP 0
#define PROTO_SCTP 1
--
2.48.1
next reply other threads:[~2025-02-21 15:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 15:06 Heming Zhao [this message]
2025-02-21 15:12 ` [PATCH] dlm_controld: Support for extended value of kernel Heming Zhao
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=20250221150611.21167-1-heming.zhao@suse.com \
--to=heming.zhao@suse.com \
--cc=aahringo@redhat.com \
--cc=ccaulfie@redhat.com \
--cc=gfs2@lists.linux.dev \
--cc=glass.su@suse.com \
--cc=jfriesse@redhat.com \
--cc=nicholas.yang@suse.com \
--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