From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org
Cc: Greg Kurz <groug@kaod.org>
Subject: 9p: requests efficiency
Date: Fri, 15 Nov 2019 02:10:50 +0100 [thread overview]
Message-ID: <1686691.fQlv7Ls6oC@silver> (raw)
I'm currently reading up on how client requests (T messages) are currently
dispatched in general by 9pfs, to understand where potential inefficiencies
are that I am encountering.
I mean 9pfs is pretty fast on raw I/O (read/write requests), provided that the
message payload on guest side was chosen large enough (e.g.
trans=virtio,version=9p2000.L,msize=4194304,...), where I already come close
to my test disk's therotical maximum performance on read/write tests. But
obviously these are huge 9p requests.
However when there are a large number of (i.e. small) 9p requests, no matter
what the actual request type is, then I am encountering severe performance
issues with 9pfs and I try to understand whether this could be improved with
reasonable effort.
If I understand it correctly, each incoming request (T message) is dispatched
to its own qemu coroutine queue. So individual requests should already be
processed in parallel, right?
Best regards,
Christian Schoenebeck
next reply other threads:[~2019-11-15 1:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 1:10 Christian Schoenebeck [this message]
2019-11-15 13:26 ` 9p: requests efficiency Greg Kurz
2019-11-20 23:37 ` Christian Schoenebeck
2019-11-23 19:26 ` Christian Schoenebeck
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=1686691.fQlv7Ls6oC@silver \
--to=qemu_oss@crudebyte.com \
--cc=groug@kaod.org \
--cc=qemu-devel@nongnu.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).