From: "Emilio G. Cota" <cota@braap.org>
To: Claudio Fontana <claudio.fontana@huawei.com>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"alvise rigo" <a.rigo@virtualopensystems.com>,
"MTTCG Devel" <mttcg@listserver.greensocs.com>,
"Mark Burton" <mark.burton@greensocs.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Sergey Fedorov" <serge.fdrv@gmail.com>,
"Pranith Kumar" <bobby.prani@gmail.com>,
"KONRAD Frédéric" <fred.konrad@greensocs.com>
Subject: Re: [Qemu-devel] Any topics for today's MTTCG sync-up call?
Date: Mon, 23 May 2016 11:22:59 -0400 [thread overview]
Message-ID: <20160523152259.GA1768@flamenco> (raw)
In-Reply-To: <5742FE28.3020601@huawei.com>
On Mon, May 23, 2016 at 14:57:12 +0200, Claudio Fontana wrote:
> Hi, at some point in the past there was a set of performance benchmarks
> which were showing the improvements using mttcg, is there some update
> on that?
Any scalable parallel workload should do.
I've used the C/C++ benchmarks in synchrobench[1] extensively for
scalability benchmarking. It's not cross-compile friendly though, so for
ARM I only managed to compile a subset of its benchmarks.
[1] https://github.com/gramoli/synchrobench
Emilio
next prev parent reply other threads:[~2016-05-23 15:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 10:57 [Qemu-devel] Any topics for today's MTTCG sync-up call? Alex Bennée
2016-05-23 12:03 ` alvise rigo
2016-05-23 12:47 ` Alex Bennée
2016-05-23 12:57 ` Claudio Fontana
2016-05-23 13:16 ` Alex Bennée
2016-05-23 15:22 ` Emilio G. Cota [this message]
2016-05-23 15:28 ` Emilio G. Cota
-- strict thread matches above, loose matches on Subject: below --
2016-06-20 11:57 Alex Bennée
2016-06-20 13:01 ` alvise rigo
2016-06-20 14:12 ` Alex Bennée
2016-06-20 14:18 ` alvise rigo
2016-07-04 9:46 Alex Bennée
2016-07-04 13:08 ` Alex Bennée
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=20160523152259.GA1768@flamenco \
--to=cota@braap.org \
--cc=a.rigo@virtualopensystems.com \
--cc=alex.bennee@linaro.org \
--cc=bobby.prani@gmail.com \
--cc=claudio.fontana@huawei.com \
--cc=fred.konrad@greensocs.com \
--cc=mark.burton@greensocs.com \
--cc=mttcg@listserver.greensocs.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=serge.fdrv@gmail.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).