From: Stefan Hajnoczi <stefanha@gmail.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: qemu-devel@nongnu.org, vgoyal@redhat.com,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/2] virtio: add vhost-user-fs base device
Date: Fri, 23 Aug 2019 10:25:51 +0100 [thread overview]
Message-ID: <20190823092551.GA12092@stefanha-x1.localdomain> (raw)
In-Reply-To: <20190822111916.735fd3ce.cohuck@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2520 bytes --]
On Thu, Aug 22, 2019 at 11:19:16AM +0200, Cornelia Huck wrote:
> On Thu, 22 Aug 2019 09:52:37 +0100
> Stefan Hajnoczi <stefanha@redhat.com> wrote:
>
> > On Wed, Aug 21, 2019 at 08:11:18PM +0100, Dr. David Alan Gilbert wrote:
> > > * Michael S. Tsirkin (mst@redhat.com) wrote:
> > > > On Fri, Aug 16, 2019 at 03:33:20PM +0100, Dr. David Alan Gilbert (git) wrote:
>
> > > > > +static void vuf_device_realize(DeviceState *dev, Error **errp)
> > > > > +{
> > > > > + VirtIODevice *vdev = VIRTIO_DEVICE(dev);
> > > > > + VHostUserFS *fs = VHOST_USER_FS(dev);
> > > > > + unsigned int i;
> > > > > + size_t len;
> > > > > + int ret;
> > > > > +
> > > > > + if (!fs->conf.chardev.chr) {
> > > > > + error_setg(errp, "missing chardev");
> > > > > + return;
> > > > > + }
> > > > > +
> > > > > + if (!fs->conf.tag) {
> > > > > + error_setg(errp, "missing tag property");
> > > > > + return;
> > > > > + }
> > > > > + len = strlen(fs->conf.tag);
> > > > > + if (len == 0) {
> > > > > + error_setg(errp, "tag property cannot be empty");
> > > > > + return;
> > > > > + }
> > > > > + if (len > sizeof_field(struct virtio_fs_config, tag)) {
> > > > > + error_setg(errp, "tag property must be %zu bytes or less",
> > > > > + sizeof_field(struct virtio_fs_config, tag));
> > > > > + return;
> > > > > + }
> > > > > +
> > > > > + if (fs->conf.num_queues == 0) {
> > > > > + error_setg(errp, "num-queues property must be larger than 0");
> > > > > + return;
> > > > > + }
> > > >
> > > > The strange thing is that actual # of queues is this number + 2.
> > > > And this affects an optimal number of vectors (see patch 2).
> > > > Not sure what a good solution is - include the
> > > > mandatory queues in the number?
> > > > Needs to be documented in some way.
> > >
> > > Should we be doing nvectors the same way virtio-scsi-pci does it;
> > > with a magic 'unspecified' default where it sets the nvectors based on
> > > the number of queues?
> > >
> > > I think my preference is not to show the users the mandatory queues.
> >
> > I agree. Users want to control multiqueue, not on the absolute number
> > of virtqueues including mandatory queues.
>
> I agree as well, but let me advocate again for renaming this to
> 'num_request_queues' or similar to make it more obvious what this number
> actually means.
Good idea.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-08-23 9:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 14:33 [Qemu-devel] [PATCH 0/2] Add virtio-fs (experimental) Dr. David Alan Gilbert (git)
2019-08-16 14:33 ` [Qemu-devel] [PATCH 1/2] virtio: add vhost-user-fs base device Dr. David Alan Gilbert (git)
2019-08-18 11:08 ` Michael S. Tsirkin
2019-08-20 12:24 ` Cornelia Huck
2019-08-20 13:39 ` Dr. David Alan Gilbert
2019-08-21 17:52 ` Dr. David Alan Gilbert
2019-08-21 19:11 ` Dr. David Alan Gilbert
2019-08-22 8:52 ` Stefan Hajnoczi
2019-08-22 9:19 ` Cornelia Huck
2019-08-23 9:25 ` Stefan Hajnoczi [this message]
2019-09-17 9:21 ` Dr. David Alan Gilbert
2019-08-16 14:33 ` [Qemu-devel] [PATCH 2/2] virtio: add vhost-user-fs-pci device Dr. David Alan Gilbert (git)
2019-08-16 18:38 ` [Qemu-devel] [PATCH 0/2] Add virtio-fs (experimental) no-reply
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=20190823092551.GA12092@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=cohuck@redhat.com \
--cc=dgilbert@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=vgoyal@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).