qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Denis Plotnikov <dplotnikov@virtuozzo.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: kwolf@redhat.com, fam@euphon.net, ehabkost@redhat.com,
	qemu-block@nongnu.org, mst@redhat.com, qemu-devel@nongnu.org,
	mreitz@redhat.com, pbonzini@redhat.com
Subject: Re: [PATCH v2] virtio: increase virtuqueue size for virtio-scsi and virtio-blk
Date: Tue, 18 Feb 2020 17:03:58 +0300	[thread overview]
Message-ID: <79647178-9fc5-6e78-b67f-cf00e399cd43@virtuozzo.com> (raw)
In-Reply-To: <490fc138-f0c8-8daa-96a0-eb3f6067fef7@virtuozzo.com>



On 18.02.2020 16:59, Denis Plotnikov wrote:
>
>
> On 18.02.2020 16:53, Stefan Hajnoczi wrote:
>> On Thu, Feb 13, 2020 at 05:59:27PM +0300, Denis Plotnikov wrote:
>>> v1:
>>>    * seg_max default value changing removed
>>>
>>> ---
>>> The goal is to reduce the amount of requests issued by a guest on
>>> 1M reads/writes. This rises the performance up to 4% on that kind of
>>> disk access pattern.
>>>
>>> The maximum chunk size to be used for the guest disk accessing is
>>> limited with seg_max parameter, which represents the max amount of
>>> pices in the scatter-geather list in one guest disk request.
>>>
>>> Since seg_max is virqueue_size dependent, increasing the virtqueue
>>> size increases seg_max, which, in turn, increases the maximum size
>>> of data to be read/write from a guest disk.
>>>
>>> More details in the original problem statment:
>>> https://lists.gnu.org/archive/html/qemu-devel/2017-12/msg03721.html
>>>
>>> Suggested-by: Denis V. Lunev <den@openvz.org>
>>> Signed-off-by: Denis Plotnikov <dplotnikov@virtuozzo.com>
>>> ---
>>>   hw/block/virtio-blk.c | 2 +-
>>>   hw/core/machine.c     | 2 ++
>>>   hw/scsi/virtio-scsi.c | 2 +-
>>>   3 files changed, 4 insertions(+), 2 deletions(-)
>> I fixed up the "virtuqueue" typo in the commit message and the
>> mis-formatted commit description (git-am(1) stops including lines after
>> the first "---").
> Actually, I sent the corrected version v3 of the patch last week. But 
> it seems it got lost among that gigantic patch flow in the mailing 
> list :)
> Thanks for applying!
>
> Denis
>>
>> Thanks, applied to my block tree:
>> https://github.com/stefanha/qemu/commits/block
>>
>> Stefan
I'm going to send the test checking the virtqueue-sizes for machine 
types a little bit later.

Denis



  reply	other threads:[~2020-02-18 14:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-13 14:59 [PATCH v2] virtio: increase virtuqueue size for virtio-scsi and virtio-blk Denis Plotnikov
2020-02-13 15:43 ` Philippe Mathieu-Daudé
2020-02-18 13:53 ` Stefan Hajnoczi
2020-02-18 13:59   ` Denis Plotnikov
2020-02-18 14:03     ` Denis Plotnikov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-02-11 14:14 Denis Plotnikov
2020-02-12 15:43 ` Stefan Hajnoczi
2020-02-13  8:08   ` Denis Plotnikov
2020-02-13  9:08     ` Stefan Hajnoczi
2020-02-13  9:28       ` Denis Plotnikov
2020-02-13 11:45         ` Stefan Hajnoczi
2020-02-13 12:41           ` Denis Plotnikov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=79647178-9fc5-6e78-b67f-cf00e399cd43@virtuozzo.com \
    --to=dplotnikov@virtuozzo.com \
    --cc=ehabkost@redhat.com \
    --cc=fam@euphon.net \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).