From: Christian Schoenebeck <linux_oss@crudebyte•com>
To: v9fs-developer@lists•sourceforge.net
Cc: netdev@vger•kernel.org,
Dominique Martinet <asmadeus@codewreck•org>,
Eric Van Hensbergen <ericvh@gmail•com>,
Latchesar Ionkov <lucho@ionkov•net>, Greg Kurz <groug@kaod•org>,
Vivek Goyal <vgoyal@redhat•com>
Subject: [PATCH v2 0/7] net/9p: remove msize limit in virtio transport
Date: Mon, 20 Sep 2021 18:43:30 +0200 [thread overview]
Message-ID: <cover.1632156835.git.linux_oss@crudebyte.com> (raw)
This series aims to get get rid of the current 500k 'msize' limitation in
the 9p virtio transport, which is currently a bottleneck for performance
of 9p mounts.
This is a follow-up of the following series and discussion:
https://lore.kernel.org/all/28bb651ae0349a7d57e8ddc92c1bd5e62924a912.1630770829.git.linux_oss@crudebyte.com/T/#eb647d0c013616cee3eb8ba9d87da7d8b1f476f37
Known limitation: With this series applied I can run
QEMU host <-> 9P virtio <-> Linux guest
with up to 3 MB msize. If I try to run it with 4 MB it seems to hit some
limitation on QEMU side:
qemu-system-x86_64: virtio: too many write descriptors in indirect table
I haven't looked into this issue yet.
Testing and feedback appreciated!
v1 -> v2:
* Fix memory leak [patch 6].
* Use pr_info() instead of p9_debug(P9_DEBUG_ERROR, ...) for user info
[patch 1].
* Show user info message if chained SG lists are not supported on
architecture [patch 6].
* Kernel doc fixes [patch 4], [patch 6].
Christian Schoenebeck (7):
net/9p: show error message if user 'msize' cannot be satisfied
9p/trans_virtio: separate allocation of scatter gather list
9p/trans_virtio: turn amount of sg lists into runtime info
9p/trans_virtio: introduce struct virtqueue_sg
net/9p: add trans_maxsize to struct p9_client
9p/trans_virtio: support larger msize values
9p/trans_virtio: resize sg lists to whatever is possible
include/net/9p/client.h | 2 +
net/9p/client.c | 17 ++-
net/9p/trans_virtio.c | 290 ++++++++++++++++++++++++++++++++++------
3 files changed, 269 insertions(+), 40 deletions(-)
--
2.20.1
next reply other threads:[~2021-09-20 18:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-20 16:43 Christian Schoenebeck [this message]
2021-09-20 16:43 ` [PATCH v2 1/7] net/9p: show error message if user 'msize' cannot be satisfied Christian Schoenebeck
2021-09-20 16:43 ` [PATCH v2 2/7] 9p/trans_virtio: separate allocation of scatter gather list Christian Schoenebeck
2021-09-20 16:43 ` [PATCH v2 3/7] 9p/trans_virtio: turn amount of sg lists into runtime info Christian Schoenebeck
2021-09-20 16:44 ` [PATCH v2 4/7] 9p/trans_virtio: introduce struct virtqueue_sg Christian Schoenebeck
2021-09-22 11:25 ` Christian Schoenebeck
2021-09-20 16:44 ` [PATCH v2 5/7] net/9p: add trans_maxsize to struct p9_client Christian Schoenebeck
2021-09-20 16:44 ` [PATCH v2 6/7] 9p/trans_virtio: support larger msize values Christian Schoenebeck
2021-09-22 11:42 ` Christian Schoenebeck
2021-09-20 16:44 ` [PATCH v2 7/7] 9p/trans_virtio: resize sg lists to whatever is possible Christian Schoenebeck
2021-09-22 11:56 ` 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=cover.1632156835.git.linux_oss@crudebyte.com \
--to=linux_oss@crudebyte$(echo .)com \
--cc=asmadeus@codewreck$(echo .)org \
--cc=ericvh@gmail$(echo .)com \
--cc=groug@kaod$(echo .)org \
--cc=lucho@ionkov$(echo .)net \
--cc=netdev@vger$(echo .)kernel.org \
--cc=v9fs-developer@lists$(echo .)sourceforge.net \
--cc=vgoyal@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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