From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>
Cc: Greg Kurz <groug@kaod.org>
Subject: [PULL 0/2] 9p queue
Date: Tue, 15 Sep 2020 12:38:01 +0200 [thread overview]
Message-ID: <cover.1600166281.git.qemu_oss@crudebyte.com> (raw)
The following changes since commit 2d2c73d0e3d504a61f868e46e6abd5643f38091b:
Merge remote-tracking branch 'remotes/pmaydell/tags/pull-target-arm-20200914-1' into staging (2020-09-14 16:03:08 +0100)
are available in the Git repository at:
https://github.com/cschoenebeck/qemu.git tags/pull-9p-20200915
for you to fetch changes up to c418f935ac6aed9aa1dc0ceb4b19044a9b7b7968:
9pfs: disable msize warning for synth driver (2020-09-15 12:12:03 +0200)
----------------------------------------------------------------
The intention of the following two patches is making users aware about
the negative file I/O performance impact when using a very low value
for 9P client parameter 'msize', which especially is the case if no
'msize' parameter was supplied by the user with a 9P Linux client at all.
All it does is logging a performance warning on host side (once) in
that case. By setting 'msize' on client side to any value larger than
8192 the performance warning will disappear.
See https://wiki.qemu.org/Documentation/9psetup#msize for details.
----------------------------------------------------------------
Christian Schoenebeck (2):
9pfs: log warning if msize <= 8192
9pfs: disable msize warning for synth driver
fsdev/file-op-9p.h | 4 ++++
hw/9pfs/9p-synth.c | 2 ++
hw/9pfs/9p.c | 9 +++++++++
3 files changed, 15 insertions(+)
next reply other threads:[~2020-09-16 9:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 10:38 Christian Schoenebeck [this message]
2020-09-03 14:20 ` [PULL 1/2] 9pfs: log warning if msize <= 8192 Christian Schoenebeck
2020-09-06 16:50 ` [PULL 2/2] 9pfs: disable msize warning for synth driver Christian Schoenebeck
2020-09-16 15:25 ` [PULL 0/2] 9p queue Peter Maydell
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.1600166281.git.qemu_oss@crudebyte.com \
--to=qemu_oss@crudebyte.com \
--cc=groug@kaod.org \
--cc=peter.maydell@linaro.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).