public inbox for gfs2@lists.linux.dev
 help / color / mirror / Atom feed
From: christine caulfield <ccaulfie@redhat.com>
To: Alexander Aring <aahringo@redhat.com>,
	Heming Zhao <heming.zhao@suse.com>
Cc: teigland@redhat.com, jfriesse@redhat.com, nicholas.yang@suse.com,
	glass.su@suse.com, gfs2@lists.linux.dev,
	Roger Zhou <ZZhou@suse.com>
Subject: Re: [PATCH v2 1/1] dlm_controld: support corosync3/knet multi-link
Date: Fri, 17 Jan 2025 15:16:51 +0000	[thread overview]
Message-ID: <54d17bad-997e-4271-9d76-679a923b4ea8@redhat.com> (raw)
In-Reply-To: <CAK-6q+grrJ5K7FTRnyFatZLTq726s5Y_S8CoKXWywedUTzp3rQ@mail.gmail.com>

On 17/01/2025 15:11, Alexander Aring wrote:
> Hi,
> 
> On Sun, Jan 12, 2025 at 10:13 PM Heming Zhao <heming.zhao@suse.com> wrote:
> ...
>>
>> The current dlm code design doesn't allow reconfiguring the network
>> protocol on the fly. In the above scenario, the dlm will maintain the
>> TCP connection until the next dlm_deamon restart.
>>
>> In my view, it's not essential for dlm to follow the knet dynamically
>> multi-link style. if the user hasn't set the 'protocol' item in
>> dlm.conf, (with my patch, for knet env), dlm will detect the corosync
>> nodelist on startup, and set the appropriate protocol mode.
>>
>> If the user want to keep maintain a multi-link for dlm, they should
>> set protocl item in dlm.conf.
>>
>> On the other hand, if dlm needs to dynamically change the number of
>> links during runtime, it should always use the SCTP protocol.
> 
> to move on here, I would at first apply/ack the patches for the static
> maximum address increase.
> 
> I see no problems to do that as this is required by you.
> 
> For the automatic protocol detection and corosync3, at least I need to
> doing some tests as I have currently 0 ideas how corosync informs the
> users about new/removed links during runtime.
> 

To be honest, it mostly doesn't - and it's maybe something we could look 
into, though I doubt it would be high priority as this is the first time 
it's been thought of :)

Currently you can watch for the cmap key config.reload_in_progress and 
after that goes from 1 back to 0 re-read the new corosync.conf.

Chrissie

> - Alex
> 


  reply	other threads:[~2025-01-17 15:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-24  8:42 [PATCH 0/1] dlm_tools: support corosync3/knet multi-link Heming Zhao
2024-12-24  8:42 ` [PATCH v2 1/1] dlm_controld: " Heming Zhao
2025-01-06 18:11   ` Alexander Aring
2025-01-07  4:59     ` Heming Zhao
2025-01-08 15:54       ` Alexander Aring
2025-01-09  2:26         ` Heming Zhao
2025-01-09 15:34           ` Alexander Aring
2025-01-09 15:38             ` christine caulfield
2025-01-10 14:28             ` Heming Zhao
2025-01-10 14:43               ` christine caulfield
2025-01-13  3:12                 ` Heming Zhao
2025-01-17 15:11                   ` Alexander Aring
2025-01-17 15:16                     ` christine caulfield [this message]
2025-02-18 11:46                       ` Heming Zhao
2025-02-18 16:35                         ` Alexander Aring
2025-02-20  3:56                           ` 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=54d17bad-997e-4271-9d76-679a923b4ea8@redhat.com \
    --to=ccaulfie@redhat.com \
    --cc=ZZhou@suse.com \
    --cc=aahringo@redhat.com \
    --cc=gfs2@lists.linux.dev \
    --cc=glass.su@suse.com \
    --cc=heming.zhao@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