search for: elementsiothreadsallocation

2015-11-19 16:09 GMT+03:00 John Ferlan <jferlan@redhat.com>: > Check out virsh iothread{info|pin|add|del} and of course the > corresponding virDomain{Add|Pin|Del}IOThread and virDomainGetIOThreadInfo. Yes, thanks! Does in near feature libvirt devs integrate this ability to domain format? As i understand all qemu stable features supported by libvirt. And data plane for virtio-blk is

2015-11-30 14:17 GMT+03:00 John Ferlan <jferlan@redhat.com>: > Such as? > > http://libvirt.org/formatdomain.html#elementsIOThreadsAllocation > > and usage within <cputune> as <iothreadpin> or <iothreadsched> So you mean that if i define iothread in domain xml and create virtio-scsi it automatic enables virtio-scsi-data-plane? -- Vasiliy Tolstov, e-mail: v.tolstov@selfip.ru

...readInfo. > > > Yes, thanks! Does in near feature libvirt devs integrate this ability > to domain format? As i understand all qemu stable features supported > by libvirt. And data plane for virtio-blk is stable for some time.... > Such as? http://libvirt.org/formatdomain.html#elementsIOThreadsAllocation and usage within <cputune> as <iothreadpin> or <iothreadsched> John

On 11/30/2015 06:23 AM, Vasiliy Tolstov wrote: > 2015-11-30 14:17 GMT+03:00 John Ferlan <jferlan@redhat.com>: >> Such as? >> >> http://libvirt.org/formatdomain.html#elementsIOThreadsAllocation >> >> and usage within <cputune> as <iothreadpin> or <iothreadsched> > > > So you mean that if i define iothread in domain xml and create > virtio-scsi it automatic enables virtio-scsi-data-plane? > As long as the qemu you're using supports the...

On 12/06/2016 06:06 AM, Blair Bethwaite wrote: > Hi Roberto, Hi Blair > What is the cpu and memory configuration of your guest? I've set to copy host configuration (16 cores) and memory is set to 24GB, host has 64GB. Guest is Windows 2012 64bits version Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 16

...e is qemu I/O loop, I'd say. Without iothreads qemu has only one I/O loop and thus if your guest issues writes from all 32 cores at once this loop is unable to handle it (performance wise) and therefore the performance drop. You can try enabling iothreads: https://libvirt.org/formatdomain.html#elementsIOThreadsAllocation This is a qemu feature that allows you to create more I/O threads and also pin them. This is an example how to use them: https://libvirt.org/git/?p=libvirt.git;a=blob;f=tests/qemuxml2argvdata/iothreads-disk.xml;h=0aa32c392300c0a86ad26185292ebc7a0d85d588;hb=HEAD And this is an example how to pin...

...;d say. Without iothreads qemu has only one I/O loop and thus if > your guest issues writes from all 32 cores at once this loop is unable > to handle it (performance wise) and therefore the performance drop. You > can try enabling iothreads: > > https://libvirt.org/formatdomain.html#elementsIOThreadsAllocation > > This is a qemu feature that allows you to create more I/O threads and > also pin them. This is an example how to use them: > > https://libvirt.org/git/?p=libvirt.git;a=blob;f=tests/qemuxml2argvdata/iothreads-disk.xml;h=0aa32c392300c0a86ad26185292ebc7a0d85d588;hb=HEAD > >...

Hello, I have cluster with AMD EPYC 7351 cpu. Two CPUs per node. I have performance 8-NUMA configuration: This is from hypervizor: [root@hde10 ~]# lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 64 On-line CPU(s) list: 0-63 Thread(s) per core: 2 Core(s) per socket: 16 Socket(s): 2 NUMA