linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: David Teigland <teigland@redhat.com>
To: Gang He <GHe@suse.com>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] questions about dlm: add TCP multihoming/failover support
Date: Tue, 24 Sep 2019 09:45:06 -0500	[thread overview]
Message-ID: <20190924144506.GB24560@redhat.com> (raw)
In-Reply-To: <CH2PR18MB320633BFA3C024C348A1F91ECF840@CH2PR18MB3206.namprd18.prod.outlook.com>

On Tue, Sep 24, 2019 at 09:04:56AM +0000, Gang He wrote:
> Hello List,
> 
> When I tried to upgrade libdlm to v4.0.9, I can see one commit for add TCP multihoming/failover support. 
> commit 7a273b8714da400d292d6c9762acedcde1997e52
> Author: David Windsor <dwindsor@redhat.com>
> Date:   Tue May 7 09:56:53 2019 -0400
>     dlm_controld: bind to all interfaces for failover 
> 
> According to the commit description, I can find there are some kernel related patches(fs/dlm in kernel space).
> e.g. 
> https://www.redhat.com/archives/cluster-devel/2019-January/msg00009.html
> https://www.redhat.com/archives/cluster-devel/2019-January/msg00010.html
> 
> But, so far, these kernel patches have not been in Torvalds kernel git tree.
> That means we cannot use this feature, although we upgrade libdlm to v4.0.9?
> 
> Second, how to use this feature after these kernel patch are available? There is any document to guide the use to use(or test) this feature?

The project was never completed and seems to be abandoned. I will revert
that dlm_controld commit if it's never used for anything.

      reply	other threads:[~2019-09-24 14:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-24  9:04 [linux-lvm] questions about dlm: add TCP multihoming/failover support Gang He
2019-09-24 14:45 ` David Teigland [this message]

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=20190924144506.GB24560@redhat.com \
    --to=teigland@redhat.com \
    --cc=GHe@suse.com \
    --cc=linux-lvm@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).