sanlock-devel November 2020

sanlock-devel@lists.fedorahosted.org

3 participants
2 discussions

[sanlock] branch master updated: config: Add max_worker_threads
by pagure＠pagure.io 30 Nov '20

30 Nov '20

This is an automated email from the git hooks/post-receive script. teigland pushed a commit to branch master in repository sanlock. The following commit(s) were added to refs/heads/master by this push: new e722c69 config: Add max_worker_threads e722c69 is described below commit e722c69cef883af1f7d60cbb2708f0092dbf2ab0 Author: Nir Soffer <nsoffer(a)redhat.com> AuthorDate: Mon Nov 30 15:02:33 2020 -0600 config: Add max_worker_threads Concurrent async add_lockspace calls are limited by the number of worker threads. Using larger number of worker threads shorten the time to add many locksapces in large setups. Previously this value could be modified only via the command line. Now it can be modified via the sanlock configuration file for easier deployment. Buglink: https://bugzilla.redhat.com/1902468 Signed-off-by: Nir Soffer <nsoffer(a)redhat.com> --- src/main.c | 7 +++++++ src/sanlock.8 | 5 +++++ src/sanlock.conf | 3 +++ 3 files changed, 15 insertions(+) diff --git a/src/main.c b/src/main.c index e2901f3..63d8cff 100644 --- a/src/main.c +++ b/src/main.c @@ -2877,6 +2877,13 @@ static void read_config_file(void) } else { log_error("ignore unknown max_sectors_kb %s", str); } + + } else if (!strcmp(str, "max_worker_threads")) { + get_val_int(line, &val); + if (val < DEFAULT_MIN_WORKER_THREADS) + val = DEFAULT_MIN_WORKER_THREADS; + com.max_worker_threads = val; + } } diff --git a/src/sanlock.8 b/src/sanlock.8 index a9126a4..2021b4a 100644 --- a/src/sanlock.8 +++ b/src/sanlock.8 @@ -1372,6 +1372,11 @@ The io timeout to use when initializing ondisk lease structures for a lockspace or resource. This timeout is not used as a part of either lease algorithm (as the standard io_timeout is.) +.IP \[bu] 2 +max_worker_threads = <num> +.br +See -t + .SH SEE ALSO .BR wdmd (8) diff --git a/src/sanlock.conf b/src/sanlock.conf index 9b78e5c..2909a9c 100644 --- a/src/sanlock.conf +++ b/src/sanlock.conf @@ -66,3 +66,6 @@ # # write_init_io_timeout = <seconds> # command line: n/a +# +# max_worker_threads = 8 +# command line: -t 8 -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 0

[PATCH] config: Add max_worker_threads
by Nir Soffer 30 Nov '20

30 Nov '20

Concurrent async add_lockspace calls are limited by the number of worker threads. Using larger number of worker threads shorten the time to add many locksapces in large setups. Previously this value could be modified only via the command line. Now it can be modified via the sanlock configuration file for easier deployment. Buglink: https://bugzilla.redhat.com/1902468 Signed-off-by: Nir Soffer <nsoffer(a)redhat.com> --- src/main.c | 7 +++++++ src/sanlock.conf | 3 +++ 2 files changed, 10 insertions(+) diff --git a/src/main.c b/src/main.c index e2901f3..63d8cff 100644 --- a/src/main.c +++ b/src/main.c @@ -2877,6 +2877,13 @@ static void read_config_file(void) } else { log_error("ignore unknown max_sectors_kb %s", str); } + + } else if (!strcmp(str, "max_worker_threads")) { + get_val_int(line, &val); + if (val < DEFAULT_MIN_WORKER_THREADS) + val = DEFAULT_MIN_WORKER_THREADS; + com.max_worker_threads = val; + } } diff --git a/src/sanlock.conf b/src/sanlock.conf index 9b78e5c..2909a9c 100644 --- a/src/sanlock.conf +++ b/src/sanlock.conf @@ -66,3 +66,6 @@ # # write_init_io_timeout = <seconds> # command line: n/a +# +# max_worker_threads = 8 +# command line: -t 8 -- 2.26.2

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

sanlock-devel November 2020