From: Stefan Hajnoczi <stefanha@redhat.com>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: German Maglione <gmaglione@redhat.com>,
virtualization@lists.linux-foundation.org,
Jonas Pfefferle <JPF@zurich.ibm.com>,
miklos@szeredi.hu
Subject: Re: virtio-fs: adding support for multi-queue
Date: Tue, 7 Feb 2023 16:32:02 -0500 [thread overview]
Message-ID: <Y+LDUmWyXCdPIriB@fedora> (raw)
In-Reply-To: <Y+KsVhIR9aEoSdRu@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 976 bytes --]
On Tue, Feb 07, 2023 at 02:53:58PM -0500, Vivek Goyal wrote:
> On Tue, Feb 07, 2023 at 02:45:39PM -0500, Stefan Hajnoczi wrote:
> > On Tue, Feb 07, 2023 at 11:14:46AM +0100, Peter-Jan Gootzen wrote:
> > > Hi,
> > >
>
> [cc German]
>
> > > For my MSc thesis project in collaboration with IBM
> > > (https://github.com/IBM/dpu-virtio-fs) we are looking to improve the
> > > performance of the virtio-fs driver in high throughput scenarios. We think
> > > the main bottleneck is the fact that the virtio-fs driver does not support
> > > multi-queue (while the spec does). A big factor in this is that our setup on
> > > the virtio-fs device-side (a DPU) does not easily allow multiple cores to
> > > tend to a single virtio queue.
>
> This is an interesting limitation in DPU.
Virtqueues are single-consumer queues anyway. Sharing them between
multiple threads would be expensive. I think using multiqueue is natural
and not specific to DPUs.
Stefan
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 183 bytes --]
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2023-02-07 21:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2fd99bc2-0414-0b85-2bff-3a84ae6c23bd@gootzen.net>
2023-02-07 19:45 ` virtio-fs: adding support for multi-queue Stefan Hajnoczi
2023-02-07 19:53 ` Vivek Goyal
2023-02-07 21:32 ` Stefan Hajnoczi [this message]
2023-02-07 21:57 ` Vivek Goyal
2023-02-08 8:33 ` Peter-Jan Gootzen via Virtualization
2023-02-08 10:43 ` Stefan Hajnoczi
2023-02-08 16:29 ` Peter-Jan Gootzen via Virtualization
2023-02-08 20:23 ` Vivek Goyal
2023-02-22 14:32 ` Stefan Hajnoczi
2023-03-07 19:43 ` Peter-Jan Gootzen via Virtualization
2023-03-07 22:26 ` Vivek Goyal
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=Y+LDUmWyXCdPIriB@fedora \
--to=stefanha@redhat.com \
--cc=JPF@zurich.ibm.com \
--cc=gmaglione@redhat.com \
--cc=miklos@szeredi.hu \
--cc=vgoyal@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
/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).