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

Marc Hartmayer mhartmay at linux.ibm.com
Fri Jul 20 07:48:48 UTC 2018


On Thu, Jul 19, 2018 at 04:53 PM +0200, John Ferlan <jferlan at redhat.com> wrote:
> 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 at linux.ibm.com>
>> Reviewed-by: Boris Fiuczynski <fiuczy at linux.ibm.com>
>> Reviewed-by: Bjoern Walk <bwalk at 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.

Yep. Thanks for reviewing.

>
> Reviewed-by: John Ferlan <jferlan at redhat.com>
>
> John
>
--
Beste Grüße / Kind regards
   Marc Hartmayer

IBM Deutschland Research & Development GmbH
Vorsitzende des Aufsichtsrats: Martina Koederitz
Geschäftsführung: Dirk Wittkopp
Sitz der Gesellschaft: Böblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294





More information about the libvir-list mailing list