[sanlock] 01/01: config: Add max_worker_threads

This is an automated email from the git hooks/post-receive script.

nsoffer pushed a commit to annotated tag config-v1
in repository sanlock.

commit 96f282c7b055e4856ee010d1b664179e33137c6c
Author: Nir Soffer 
AuthorDate: Mon Nov 30 20:40:38 2020 +0200

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 
---
 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

[Nir Soffer]

I pushed local tags to pagure by mistake while trying to fix the
sanlock-3.8.3 tag.

Sorry for the noise.

On Wed, May 19, 2021 at 3:21 PM  wrote:
> This is an automated email from the git hooks/post-receive script.
>
> nsoffer pushed a commit to annotated tag config-v1
> in repository sanlock.
>
> commit 96f282c7b055e4856ee010d1b664179e33137c6c
> Author: Nir Soffer 
> AuthorDate: Mon Nov 30 20:40:38 2020 +0200
> 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 <[e-mail]>
>
> 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
>
> --
> To stop receiving notification emails like this one, please contact
> the administrator of this repository.
> _______________________________________________
> sanlock-devel mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedorahosted.org/archives/list/[e-mail]...
> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure