Re: [libvirt] [PATCH v2 3/6] virThreadPool: Prevent switching between zero and non-zero maxWorkers

On 07/03/2018 07:37 AM, Marc Hartmayer wrote:

...since maxWorkers=0 is only intended for virtlockd or virlogd which must not be multithreaded.

Signed-off-by: Marc Hartmayer <mhartmay@linux.ibm.com> Reviewed-by: Boris Fiuczynski <fiuczy@linux.ibm.com> Reviewed-by: Bjoern Walk <bwalk@linux.ibm.com> --- src/util/virthreadpool.c | 8 ++++++++ 1 file changed, 8 insertions(+)

I think this is separable - this could be pushed regardless of the outcome of patch2, right? Let me know - I can reduce the load the next update based on patch2 comments. Reviewed-by: John Ferlan <jferlan@redhat.com> John