mirror of
https://github.com/libvirt/libvirt.git
synced 2025-02-25 18:55:26 -06:00
conf: Introduce thread_pool_min and thread_pool_max attributes to IOThread
At least in case of QEMU an IOThread is actually a pool of threads (see iothread_set_aio_context_params() in QEMU's code base). As such, it can have minimal and maximal number of worker threads. Allow setting them in domain XML. Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Peter Krempa <pkrempa@redhat.com>
This commit is contained in:
@@ -675,7 +675,7 @@ host/guest with many LUNs. :since:`Since 1.2.8 (QEMU only)`
|
||||
<iothread id="2"/>
|
||||
<iothread id="4"/>
|
||||
<iothread id="6"/>
|
||||
<iothread id="8"/>
|
||||
<iothread id="8" thread_pool_min="2" thread_pool_max="32"/>
|
||||
</iothreadids>
|
||||
...
|
||||
</domain>
|
||||
@@ -696,6 +696,10 @@ host/guest with many LUNs. :since:`Since 1.2.8 (QEMU only)`
|
||||
any predefined ``id``. If there are more ``iothreadids`` defined than
|
||||
``iothreads`` defined for the domain, then the ``iothreads`` value will be
|
||||
adjusted accordingly. :since:`Since 1.2.15`
|
||||
The element has two optional attributes ``thread_pool_min`` and
|
||||
``thread_pool_max`` which allow setting lower and upper boundary for number
|
||||
of worker threads for given IOThread. While the former can be value of zero,
|
||||
the latter can't. :since:`Since 8.5.0`
|
||||
|
||||
|
||||
CPU Tuning
|
||||
|
||||
Reference in New Issue
Block a user