From: Heming Zhao <heming.zhao@suse.com>
To: David Teigland <teigland@redhat.com>,
Alexander Aring <aahringo@redhat.com>
Cc: ccaulfie@redhat.com, jfriesse@redhat.com, nicholas.yang@suse.com,
glass.su@suse.com, gfs2@lists.linux.dev
Subject: Re: [PATCH] dlm_controld: Support for extended value of kernel DLM_MAX_ADDR_COUNT
Date: Tue, 25 Feb 2025 14:27:00 +0800 [thread overview]
Message-ID: <456aa9b1-a197-4de4-a062-2fe11bdaf179@suse.com> (raw)
In-Reply-To: <Z7zJ6OQIzC9Q20sG@redhat.com>
On 2/25/25 03:35, David Teigland wrote:
> On Mon, Feb 24, 2025 at 10:27:04AM -0500, Alexander Aring wrote:
>> What are we doing with the detect_protocol() change? You want to
>> submit the current version again? I would like to test it with
>> corosync 2 vs 3 with no configuration changes on an upgrade (if this
>> is even possible).
>
> I suggest we stop trying to detect, and always use tcp unless protocol is
> set to sctp.
>
> Dave
>
That's fine with me
For corosync 3.x, there is a lot of work to support dynamic multi-link.
However, to support config mode, the current dlm code only requires a few modifications.
- Heming
next prev parent reply other threads:[~2025-02-25 6:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 15:09 [PATCH] dlm_controld: Support for extended value of kernel DLM_MAX_ADDR_COUNT Heming Zhao
2025-02-24 15:27 ` Alexander Aring
2025-02-24 19:35 ` David Teigland
2025-02-25 6:27 ` Heming Zhao [this message]
2025-02-25 7:34 ` Heming Zhao
2025-02-25 14:19 ` Alexander Aring
2025-02-28 1:09 ` Heming Zhao
2025-02-28 15:34 ` Alexander Aring
2025-03-04 3:07 ` Heming Zhao
2025-03-04 18:04 ` Alexander Aring
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=456aa9b1-a197-4de4-a062-2fe11bdaf179@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