From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Christian Schoenebeck <qemu_oss@crudebyte.com>
Cc: qemu-devel@nongnu.org, Greg Kurz <groug@kaod.org>
Subject: Re: [PATCH] 9pfs: log warning if msize <= 8192
Date: Wed, 2 Sep 2020 13:25:47 +0100 [thread overview]
Message-ID: <20200902122547.GH403297@redhat.com> (raw)
In-Reply-To: <E1kDR8W-0001s4-Sr@lizzy.crudebyte.com>
On Wed, Sep 02, 2020 at 01:22:49PM +0200, Christian Schoenebeck wrote:
> It is essential to choose a reasonable high value for 'msize' to avoid
> severe degraded file I/O performance. This parameter has to be chosen
> on client/guest side, and a Linux client defaults to an 'msize' of only
> 8192 if the user did not explicitly specify a value for 'msize'.
>
> Unfortunately many users are not aware that they should specify an
> appropriate value for 'msize' to avoid severe performance issues, so
> log a performance warning on host side in that case to make it more
> clear.
What is a more reasonable "msize" value to pick instead of 8k ?
ie at what msize is I/O not several degraded ?
If there a reason that Linux can't pick a better default ?
>
> Signed-off-by: Christian Schoenebeck <qemu_oss@crudebyte.com>
> ---
> hw/9pfs/9p.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/hw/9pfs/9p.c b/hw/9pfs/9p.c
> index 7bb994bbf2..33e948d636 100644
> --- a/hw/9pfs/9p.c
> +++ b/hw/9pfs/9p.c
> @@ -1353,6 +1353,14 @@ static void coroutine_fn v9fs_version(void *opaque)
> goto out;
> }
>
> + /* 8192 is the default msize of Linux clients */
> + if (s->msize <= 8192) {
> + warn_report_once(
> + "9p: degraded performance: a reasonable high msize should be "
> + "chosen on client/guest side (chosen msize is <= 8192)."
> + );
> + }
> +
> marshal:
> err = pdu_marshal(pdu, offset, "ds", s->msize, &version);
> if (err < 0) {
> --
> 2.20.1
>
>
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2020-09-02 12:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 11:22 [PATCH] 9pfs: log warning if msize <= 8192 Christian Schoenebeck
2020-09-02 12:25 ` Daniel P. Berrangé [this message]
2020-09-02 12:52 ` Christian Schoenebeck
2020-09-02 13:39 ` Greg Kurz
2020-09-02 13:45 ` Daniel P. Berrangé
2020-09-02 14:08 ` Christian Schoenebeck
2020-09-02 14:10 ` Daniel P. Berrangé
2020-09-02 16:03 ` Christian Schoenebeck
2020-09-02 16:08 ` Daniel P. Berrangé
2020-09-02 16:54 ` Greg Kurz
2020-09-03 8:20 ` Christian Schoenebeck
2020-09-03 9:35 ` Greg Kurz
2020-09-03 10:57 ` Christian Schoenebeck
2020-09-02 13:58 ` 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=20200902122547.GH403297@redhat.com \
--to=berrange@redhat.com \
--cc=groug@kaod.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu_oss@crudebyte.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).