From: Peter-Jan Gootzen <pgootzen@nvidia.com>
To: "stefanha@redhat.com" <stefanha@redhat.com>,
"mszeredi@redhat.com" <mszeredi@redhat.com>
Cc: "vgoyal@redhat.com" <vgoyal@redhat.com>,
"jefflexu@linux.alibaba.com" <jefflexu@linux.alibaba.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
Yoray Zack <yorayz@nvidia.com>,
"virtualization@lists.linux.dev" <virtualization@lists.linux.dev>
Subject: Re: [PATCH] fuse: cleanup request queuing towards virtiofs
Date: Thu, 30 May 2024 13:38:36 +0000 [thread overview]
Message-ID: <bbdba78406b2288ee6a9132b1bdfcacd7b4fc37a.camel@nvidia.com> (raw)
In-Reply-To: <20240529183231.GC1203999@fedora.redhat.com>
On Wed, 2024-05-29 at 14:32 -0400, Stefan Hajnoczi wrote:
> On Wed, May 29, 2024 at 05:52:07PM +0200, Miklos Szeredi wrote:
> > Virtiofs has its own queing mechanism, but still requests are first
> > queued
> > on fiq->pending to be immediately dequeued and queued onto the
> > virtio
> > queue.
> >
> > The queuing on fiq->pending is unnecessary and might even have some
> > performance impact due to being a contention point.
> >
> > Forget requests are handled similarly.
> >
> > Move the queuing of requests and forgets into the fiq->ops->*.
> > fuse_iqueue_ops are renamed to reflect the new semantics.
> >
> > Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
> > ---
> > fs/fuse/dev.c | 159 ++++++++++++++++++++++++-----------------
> > ---
> > fs/fuse/fuse_i.h | 19 ++----
> > fs/fuse/virtio_fs.c | 41 ++++--------
> > 3 files changed, 106 insertions(+), 113 deletions(-)
>
> This is a little scary but I can't think of a scenario where directly
> dispatching requests to virtqueues is a problem.
>
> Is there someone who can run single and multiqueue virtiofs
> performance
> benchmarks?
Yes we can provide that with our BlueField DPU setup. I will review,
test and perform some experiments on the patch and get back to you all
on this with some numbers.
>
> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
- Peter-Jan
next prev parent reply other threads:[~2024-05-30 13:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 15:52 [PATCH] fuse: cleanup request queuing towards virtiofs Miklos Szeredi
2024-05-29 18:32 ` Stefan Hajnoczi
2024-05-30 9:06 ` Miklos Szeredi
2024-05-30 13:38 ` Peter-Jan Gootzen [this message]
2024-06-05 10:40 ` Peter-Jan Gootzen
2024-06-05 11:04 ` Stefan Hajnoczi
2024-05-30 3:20 ` Jingbo Xu
2024-05-30 9:00 ` Miklos Szeredi
2024-05-30 15:36 ` Jingbo Xu
2024-05-30 17:07 ` Bernd Schubert
2024-09-23 10:33 ` Lai, Yi
2024-09-23 22:48 ` Joanne Koong
2024-09-23 23:47 ` Joanne Koong
2024-09-24 8:58 ` Miklos Szeredi
2024-09-24 9:52 ` Lai, Yi
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=bbdba78406b2288ee6a9132b1bdfcacd7b4fc37a.camel@nvidia.com \
--to=pgootzen@nvidia.com \
--cc=jefflexu@linux.alibaba.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mszeredi@redhat.com \
--cc=stefanha@redhat.com \
--cc=vgoyal@redhat.com \
--cc=virtualization@lists.linux.dev \
--cc=yorayz@nvidia.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).