[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [libvirt] [PATCH REPOST 2/7] docs: clarify disk iothread support
- From: Cole Robinson <crobinso redhat com>
- To: John Ferlan <jferlan redhat com>, libvir-list redhat com
- Subject: Re: [libvirt] [PATCH REPOST 2/7] docs: clarify disk iothread support
- Date: Tue, 3 May 2016 09:25:00 -0400
On 05/02/2016 06:30 PM, John Ferlan wrote:
> Signed-off-by: John Ferlan <jferlan redhat com>
> ---
> docs/formatdomain.html.in | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/docs/formatdomain.html.in b/docs/formatdomain.html.in
> index bead624..735546e 100644
> --- a/docs/formatdomain.html.in
> +++ b/docs/formatdomain.html.in
> @@ -2561,8 +2561,9 @@
> disk to an IOThread as defined by the range for the domain
> <a href="#elementsIOThreadsAllocation"><code>iothreads</code></a>
> value. Multiple devices may be assigned to the same IOThread and
> - are numbered from 1 to the domain iothreads value.
> - <span class='since'>Since 1.2.8 (QEMU only)</span>
> + are numbered from 1 to the domain iothreads value. Available
> + only for virtio-blk-pci and virtio-blk-ccw disks.
> + <span class='since'>Since 1.2.8 (QEMU 2.1)</span>
> </li>
> </ul>
> </dd>
>
Those are qemu specific terms. I'd rather see it spelled out in libvirt terms
or something more end user readable.
I see this mirrors the <iothreads> docs, instead I think the <iothread> docs
should just defer to the per-device docs to describe what device+version
combos support iothreads, so we don't need to update that info twice.
- Cole
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]