From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org
Cc: Greg Kurz <groug@kaod.org>, berrange@redhat.com
Subject: Re: [PATCH v2 1/1] 9pfs: log warning if msize <= 8192
Date: Thu, 03 Sep 2020 18:32:54 +0200 [thread overview]
Message-ID: <2515823.gX3yQePTrF@silver> (raw)
In-Reply-To: <20200903180248.6199bb7b@bahia.lan>
On Donnerstag, 3. September 2020 18:02:48 CEST Greg Kurz wrote:
> > diff --git a/hw/9pfs/9p.c b/hw/9pfs/9p.c
> > index 7bb994bbf2..99b6f24fd6 100644
> > --- a/hw/9pfs/9p.c
> > +++ b/hw/9pfs/9p.c
> > @@ -1353,6 +1353,15 @@ static void coroutine_fn v9fs_version(void *opaque)
> >
> > goto out;
> >
> > }
> >
> > + /* 8192 is the default msize of Linux clients */
> > + if (s->msize <= 8192) {
>
> I agree that an msize of 8192 suck from a performance standpoint but
> I guess many users are msize agnostic, and they use the default value
> without even knowing it. They might not even care for performance at
> all, otherwise they'd likely ask google and they will eventually land
> on:
>
> https://wiki.qemu.org/Documentation/9psetup#Performance_Considerations
>
> But with this patch, they will now get a warning each time they start
> QEMU, maybe freak out and file reports in launchpad. So I suggest you
> turn <= into < to avoid bothering these placid users with a warning.
Mmm, that's actually precisely my intended target group: people who have never
been aware about the existence of 'msize' before.
I keep '<=' for now, I think the log message is already clear that you simply
have to make it any 'msize' > 8192 and the warning is gone.
> Anyway, it's your choice :) so if you manage to get the #msize anchor to
> work as expected:
Works now (using raw html anchor instead):
https://wiki.qemu.org/Documentation/9psetup#msize
> Reviewed-by: Greg Kurz <groug@kaod.org>
Thanks Greg!
> > + warn_report_once(
> > + "9p: degraded performance: a reasonable high msize should be
> > "
> > + "chosen on client/guest side (chosen msize is <= 8192). See "
> > + "https://wiki.qemu.org/Documentation/9psetup#msize for
> > details." + );
> > + }
> > +
> >
> > marshal:
> > err = pdu_marshal(pdu, offset, "ds", s->msize, &version);
> > if (err < 0) {
Best regards,
Christian Schoenebeck
next prev parent reply other threads:[~2020-09-03 16:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 14:41 [PATCH v2 0/1] 9pfs: log warning if msize <= 8192 Christian Schoenebeck
2020-09-03 14:20 ` [PATCH v2 1/1] " Christian Schoenebeck
2020-09-03 16:02 ` Greg Kurz
2020-09-03 16:32 ` Christian Schoenebeck [this message]
2020-09-03 15:19 ` [PATCH v2 0/1] " Greg Kurz
2020-09-03 15:41 ` Greg Kurz
2020-09-03 15:48 ` Christian Schoenebeck
2020-09-03 16:07 ` Greg Kurz
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=2515823.gX3yQePTrF@silver \
--to=qemu_oss@crudebyte.com \
--cc=berrange@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.