All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Garzarella <sgarzare@redhat.com>
To: Denis Plotnikov <den-plotnikov@yandex-team.ru>
Cc: fam@euphon.net, kwolf@redhat.com, vsementsov@virtuozzo.com,
	ehabkost@redhat.com, qemu-block@nongnu.org, mst@redhat.com,
	Stefan Hajnoczi <stefanha@gmail.com>,
	qemu-devel@nongnu.org, mreitz@redhat.com,
	Stefan Hajnoczi <stefanha@redhat.com>,
	pbonzini@redhat.com, den@virtuozzo.com
Subject: Re: [PATCH v1 2/4] virtio: increase virtuqueue size for virtio-scsi and virtio-blk
Date: Thu, 9 Sep 2021 10:28:05 +0200	[thread overview]
Message-ID: <20210909082805.et2rf7gwfczqj64q@steredhat> (raw)
In-Reply-To: <3b35a660-c577-42b6-d977-7b43c29452a6@yandex-team.ru>

On Wed, Sep 08, 2021 at 06:20:49PM +0300, Denis Plotnikov wrote:
>
>On 08.09.2021 16:22, Stefano Garzarella wrote:
>>Message bounced, I use new Denis's email address.
>>
>>On Wed, Sep 08, 2021 at 03:17:16PM +0200, Stefano Garzarella wrote:
>>>Hi Denis,
>>>I just found this discussion since we still have the following 
>>>line in hw/core/machine.c:
>>>   { "vhost-blk-device", "seg_max_adjust", "off"}
>>>
>>>IIUC it was a typo, and I think we should fix it since in the 
>>>future we can have `vhost-blk-device`.
>>>
>>>So, I think we have 2 options:
>>>1. remove that line since for now is useless
>>>2. replace with "vhost-scsi"
>>>
>>>I'm not sure which is the best, what do you suggest?
>>>
>>>Thanks,
>>>Stefano
>
>Hi Stefano
>
>I prefer to just remove the line without replacing. This will keep 
>things exactly like it is now.
>
>Replacing with "vhost-scsi" will affect seg_max (limit to 126) on 
>newly created VMs with machine types using "hw_compat_4_2" and older.
>
>Now, because of the typo (error), their seg-max is queue-size 
>dependent. I'm not sure, if replacing the line may cause any problems, 
>for example on migration: source (queue-size 256, seg max 254) -> 
>destination (queue-size 256, seg max 126). But it will definitely 
>introduce two different behaviors for VMs with "hw_compat_4_2" and 
>older. So, I'd choose the lesser of two evils and keep the things like 
>it's now.
>

Yep, make sense. It was the same concern I had.

Do you want to send a patch to remove it with this explanation?

Thanks for the clarification,
Stefano



  reply	other threads:[~2021-09-09  8:29 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-29 14:06 [PATCH v1 0/4] Increase default virtqueue size to improve performance Denis Plotnikov
2020-01-29 14:06 ` [PATCH v1 1/4] virtio: introduce VIRTQUEUE_DEFUALT_SIZE instead of hardcoded constants Denis Plotnikov
2020-01-29 17:02   ` Philippe Mathieu-Daudé
2020-01-29 17:55   ` Cornelia Huck
2020-01-30 14:56     ` Stefan Hajnoczi
2020-02-03 12:15       ` Denis Plotnikov
2020-01-30 13:38   ` Michael S. Tsirkin
2020-02-03 12:17     ` Denis Plotnikov
2020-02-03 12:51       ` Michael S. Tsirkin
2020-02-03 12:56         ` Denis Plotnikov
2020-01-29 14:07 ` [PATCH v1 2/4] virtio: increase virtuqueue size for virtio-scsi and virtio-blk Denis Plotnikov
2020-01-30 13:40   ` Michael S. Tsirkin
2020-02-03 12:18     ` Denis Plotnikov
2020-01-30 14:58   ` Stefan Hajnoczi
2020-02-04  9:59     ` Denis Plotnikov
2020-02-05 11:19       ` Stefan Hajnoczi
2020-02-07  8:48         ` Denis Plotnikov
2020-02-07 16:13           ` Stefan Hajnoczi
2020-02-09  7:49           ` Michael S. Tsirkin
2020-02-10 15:34             ` Denis Plotnikov
2020-02-11 10:32               ` Michael S. Tsirkin
2020-02-10 17:06             ` Stefan Hajnoczi
2021-09-08 13:17           ` Stefano Garzarella
2021-09-08 13:22             ` Stefano Garzarella
2021-09-08 15:20               ` Denis Plotnikov
2021-09-09  8:28                 ` Stefano Garzarella [this message]
2021-09-09 11:26                   ` Denis Plotnikov
2020-01-29 14:07 ` [PATCH v1 3/4] tests: add virtuqueue size checking to virtio_seg_max_adjust test Denis Plotnikov
2020-01-30 13:42   ` Michael S. Tsirkin
2020-02-03 12:21     ` Denis Plotnikov
2020-01-29 14:07 ` [PATCH v1 4/4] tests: rename virtio_seg_max_adjust to virtio_check_params Denis Plotnikov
2021-09-08 15:45   ` Philippe Mathieu-Daudé

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=20210909082805.et2rf7gwfczqj64q@steredhat \
    --to=sgarzare@redhat.com \
    --cc=den-plotnikov@yandex-team.ru \
    --cc=den@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@gmail.com \
    --cc=stefanha@redhat.com \
    --cc=vsementsov@virtuozzo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.