From: Paolo Bonzini <pbonzini@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
"Daniel P. Berrange" <berrange@redhat.com>
Cc: "Amit Shah" <amit.shah@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Marc-André Lureau" <marcandre.lureau@gmail.com>,
QEMU <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] exec: silence hugetlbfs warning under qtest
Date: Tue, 24 Nov 2015 15:30:23 +0100 [thread overview]
Message-ID: <5654747F.9050004@redhat.com> (raw)
In-Reply-To: <20151124162004-mutt-send-email-mst@redhat.com>
On 24/11/2015 15:25, Michael S. Tsirkin wrote:
> I'm worried that things go slow and people don't have a way to find out
> why, and documentation isn't the first place people look for when facing
> a performance issue.
>
> At the moment we call MADV_HUGEPAGE unconditionally and unfortunately
> there's no way to report it's not having the intended effect.
>
> Maybe we want a "don't enable hugepages" flag.
> That could also have the effect of suppressing the warnings.
THP is anyway slower than hugetlbfs. If people really want performance,
they need to use hugetlbfs. For everything else I'd be surprised if
they even notice.
Paolo
next prev parent reply other threads:[~2015-11-24 14:30 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 17:23 [Qemu-devel] [PATCH 1/3] tests: define qtest-obj-y before using it marcandre.lureau
2015-11-16 17:23 ` [Qemu-devel] [PATCH 2/3] tests: re-enable vhost-user-test marcandre.lureau
2015-11-16 17:23 ` [Qemu-devel] [PATCH 3/3] exec: silence hugetlbfs warning under qtest marcandre.lureau
2015-11-16 21:50 ` Michael S. Tsirkin
2015-11-17 21:32 ` Marc-André Lureau
2015-11-18 8:32 ` Markus Armbruster
2015-11-18 9:02 ` [Qemu-devel] [PATCH] " marcandre.lureau
2015-11-18 20:49 ` Michael S. Tsirkin
2015-11-23 17:40 ` Paolo Bonzini
2015-11-23 17:46 ` Daniel P. Berrange
2015-11-23 17:49 ` Daniel P. Berrange
2015-11-23 18:01 ` Marc-André Lureau
2015-11-23 18:10 ` Daniel P. Berrange
2015-11-24 14:10 ` Michael S. Tsirkin
2015-11-24 14:19 ` Daniel P. Berrange
2015-11-24 14:25 ` Michael S. Tsirkin
2015-11-24 14:30 ` Daniel P. Berrange
2015-11-24 14:30 ` Paolo Bonzini [this message]
2015-11-24 15:29 ` Michael S. Tsirkin
2015-11-24 15:09 ` Markus Armbruster
2015-11-24 14:12 ` Michael S. Tsirkin
-- strict thread matches above, loose matches on Subject: below --
2015-10-27 16:29 marcandre.lureau
2015-10-27 18:37 ` Michael S. Tsirkin
2015-10-29 9:10 ` Michael S. Tsirkin
2015-11-08 17:02 ` Michael S. Tsirkin
2015-11-09 7:50 ` Markus Armbruster
2015-11-12 11:54 ` Michael S. Tsirkin
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=5654747F.9050004@redhat.com \
--to=pbonzini@redhat.com \
--cc=amit.shah@redhat.com \
--cc=berrange@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=mst@redhat.com \
--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 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.