All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Chirantan Ekbote <chirantan@chromium.org>
Cc: "virtio-fs@redhat.com" <virtio-fs@redhat.com>,
	"misono.tomohiro@fujitsu.com" <misono.tomohiro@fujitsu.com>,
	"masayoshi.mizuma@fujitsu.com" <masayoshi.mizuma@fujitsu.com>,
	Vivek Goyal <vgoyal@redhat.com>
Subject: Re: [Virtio-fs] xfstest results for virtio-fs on aarch64
Date: Tue, 15 Oct 2019 16:57:49 +0100	[thread overview]
Message-ID: <20191015155749.GH3073@work-vm> (raw)
In-Reply-To: <CAJFHJrrqfjQqMu-K99DiBYNmD1=hB710wRZ88w--SQ0GxQv9Tw@mail.gmail.com>

* Chirantan Ekbote (chirantan@chromium.org) wrote:
> On Mon, Oct 14, 2019 at 6:11 PM Stefan Hajnoczi <stefanha@redhat.com> wrote:
> >
> > On Fri, Oct 11, 2019 at 04:36:47PM -0400, Vivek Goyal wrote:
> > > On Sat, Oct 12, 2019 at 05:13:51AM +0900, Chirantan Ekbote wrote:
> > > > On Sat, Oct 12, 2019 at 4:59 AM Vivek Goyal <vgoyal@redhat.com> wrote:
> > > > @@ -922,7 +990,8 @@ static int virtio_fs_enqueue_req(struct virtqueue
> > > > *vq, struct fuse_req *req)
> > > >  static void virtio_fs_wake_pending_and_unlock(struct fuse_iqueue *fiq)
> > > >  __releases(fiq->waitq.lock)
> > > >  {
> > > > -       unsigned queue_id = VQ_REQUEST; /* TODO multiqueue */
> > > > +       /* unsigned queue_id = VQ_REQUEST; /\* TODO multiqueue *\/ */
> > > > +       unsigned queue_id;
> > > >         struct virtio_fs *fs;
> > > >         struct fuse_conn *fc;
> > > >         struct fuse_req *req;
> > > > @@ -937,6 +1006,7 @@ __releases(fiq->waitq.lock)
> > > >         spin_unlock(&fiq->waitq.lock);
> > > >
> > > >         fs = fiq->priv;
> > > > +       queue_id = (req->in.h.unique % (fs->nvqs - 1)) + 1;
> > > >         fc = fs->vqs[queue_id].fud->fc;
> > > >
> > > >         dev_dbg(&fs->vqs[queue_id].vq->vdev->dev,
> > > >
> > > >
> > > > This is simply round-robin scheduling but even going from one to two
> > > > queues gives a significant performance improvement (especially because
> > > > crosvm doesn't support shared memory regions yet).
> > >
> > > Interesting. I thought virtiofsd is hard coded right now to support
> > > only one queue. Did you modify virtiofsd to support more than one
> > > request queue?
> >
> > Right, virtiofsd currently refuses to bring up more than 1 request
> > queue.  The code can actually handle multiqueue now but there is no
> > command-line support for it yet.  The ability to set CPU affinity for
> > virtqueue threads could be introduced at the same time as enabling
> > multiqueue.
> >
> 
> I'm not using virtiofsd.  We have our own server for crosvm, which
> supports multiple queues.

Ah excellent; is that public anywhere?

> As for the performance numbers, I don't have my test device with me
> but if I remember correctly the blogbench scores almost doubled when
> going from one queue to two queues.

Very nice.

Dave

> 
> Chirantan
> 
> _______________________________________________
> Virtio-fs mailing list
> Virtio-fs@redhat.com
> https://www.redhat.com/mailman/listinfo/virtio-fs
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK


  reply	other threads:[~2019-10-15 15:57 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-07 12:11 [Virtio-fs] xfstest results for virtio-fs on aarch64 qi.fuli
2019-10-07 14:34 ` Dr. David Alan Gilbert
2019-10-09 16:51   ` Dr. David Alan Gilbert
2019-10-10  9:57     ` qi.fuli
2019-10-11  9:21       ` Dr. David Alan Gilbert
2019-10-11 18:45       ` Chirantan Ekbote
2019-10-11 19:59         ` Vivek Goyal
2019-10-11 20:13           ` Chirantan Ekbote
2019-10-11 20:36             ` Vivek Goyal
2019-10-14  9:11               ` Stefan Hajnoczi
2019-10-15 14:58                 ` Chirantan Ekbote
2019-10-15 15:57                   ` Dr. David Alan Gilbert [this message]
2019-10-15 16:11                     ` Chirantan Ekbote
2019-10-15 16:26                       ` Dr. David Alan Gilbert
2019-10-15 17:28                         ` Boeuf, Sebastien
2019-10-15 18:21                           ` Chirantan Ekbote
2019-10-16 14:14                             ` Stefan Hajnoczi
2019-10-16 16:14                               ` Boeuf, Sebastien
2019-10-16 18:38                                 ` Stefan Hajnoczi
2019-10-17  5:19                                   ` Boeuf, Sebastien
2019-11-01 22:26                                   ` Boeuf, Sebastien
2019-11-12  9:45                                     ` Stefan Hajnoczi
     [not found]                                       ` <5238b860a8d544e59c9a827fbc26418d53482ccf.camel@intel.com>
2019-11-13 11:39                                         ` Stefan Hajnoczi
2019-11-20 16:53                                           ` Dr. David Alan Gilbert
2019-10-16 16:11                             ` Boeuf, Sebastien
2019-10-16 18:37                               ` Stefan Hajnoczi
2019-10-16 14:09                   ` Stefan Hajnoczi
2019-10-16 19:36                     ` Chirantan Ekbote
2019-10-16 19:44                       ` Vivek Goyal
2019-10-17  9:23                       ` Stefan Hajnoczi
2019-11-06 12:13 ` Dr. David Alan Gilbert
2019-11-07  8:03   ` misono.tomohiro

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=20191015155749.GH3073@work-vm \
    --to=dgilbert@redhat.com \
    --cc=chirantan@chromium.org \
    --cc=masayoshi.mizuma@fujitsu.com \
    --cc=misono.tomohiro@fujitsu.com \
    --cc=vgoyal@redhat.com \
    --cc=virtio-fs@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 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.