cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Alexander Aring <aahringo@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCHv3 dlm-tool 0/4] dlm_controld: support for mark and waitplock_recovery
Date: Thu,  9 Jul 2020 13:21:46 -0400	[thread overview]
Message-ID: <20200709172150.53643-1-aahringo@redhat.com> (raw)

Hi,

this patch series adds support for set the in-kernel socket skb mark
value over dlm_controld. There exists two kinds of socket, one listen
socket and multiple peer sockets. Both can be set via the dlm config
file via "listen_mark" or multiple entries of:

node id=$NODEID mark=$MARK

whereas $NODEID is the corosync assigned nodeid. The given mark number
can be hexadecimal or decimal.

Also it adds support to set the waitplock_recovery per cluster attribute
by setting enable_waitplock_recover over file or argument configuration.

- Alex

changes since v3:
 - add support for unsigned int default values
 - changed default value of boolean arg enable_waitplock_recover from 1
   to 0. dlm_controld was not using the default value anyway, because
   there exists a check to ignore default values and only set it when
   it's set. I changed it anyway to be consistent.
 - Let mark per node config don't abort the whole node configuration
   if open fails (e.g. older kernel) instead we skip now to try to set
   the mark value. It will show up in the log that open fails.

changes since v2:
 - remove leftover PRIu32 in nodeid configuration
 - make unsigned int values also work with file configuration, was arg
   only before
 - add support to set the waitplock_recovery switch via dlm_controld
 - remove free function of node_config, may be necessary when implement
   some kind of NOHUP and reparse config file

Alexander Aring (4):
  dlm_controld: add support for unsigned int values
  dlm_controld: set listen skb mark setting
  dlm_controld: add support for per nodeid configuration
  dlm_controld: add support for waitplock_recovery switch

 dlm_controld/Makefile      |  3 +-
 dlm_controld/action.c      | 43 ++++++++++++++++++--
 dlm_controld/config.c      | 25 ++++++++++++
 dlm_controld/dlm.conf.5    | 23 +++++++++++
 dlm_controld/dlm_daemon.h  | 13 +++++-
 dlm_controld/main.c        | 74 ++++++++++++++++++++++------------
 dlm_controld/member.c      |  6 ++-
 dlm_controld/node_config.c | 82 ++++++++++++++++++++++++++++++++++++++
 dlm_controld/node_config.h | 31 ++++++++++++++
 9 files changed, 268 insertions(+), 32 deletions(-)
 create mode 100644 dlm_controld/node_config.c
 create mode 100644 dlm_controld/node_config.h

-- 
2.26.2



             reply	other threads:[~2020-07-09 17:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-09 17:21 Alexander Aring [this message]
2020-07-09 17:21 ` [Cluster-devel] [PATCHv3 dlm-tool 1/4] dlm_controld: add support for unsigned int values Alexander Aring
2020-07-09 17:21 ` [Cluster-devel] [PATCHv3 dlm-tool 2/4] dlm_controld: set listen skb mark setting Alexander Aring
2020-07-09 17:21 ` [Cluster-devel] [PATCHv3 dlm-tool 3/4] dlm_controld: add support for per nodeid configuration Alexander Aring
2020-07-09 17:21 ` [Cluster-devel] [PATCHv3 dlm-tool 4/4] dlm_controld: add support for waitplock_recovery switch 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=20200709172150.53643-1-aahringo@redhat.com \
    --to=aahringo@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).