From: Avi Kivity <avi@redhat.com>
To: Matthieu Olivier <ppmarcel@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: Discordant results between UnixBench and nBench
Date: Wed, 23 Dec 2009 14:39:47 +0200 [thread overview]
Message-ID: <4B320F93.6080700@redhat.com> (raw)
In-Reply-To: <c59a6b1d0912230427g5d06bd7dsd7e870bfd20a4c62@mail.gmail.com>
On 12/23/2009 02:27 PM, Matthieu Olivier wrote:
>
> Ok, there is an excel file which contain some results.
> I'm not supposed to give so many informations, but I really need to
> understand what's the problem.
>
>
This is strange. Is the machine hyperthreaded?
Please supply full /proc/cpuinfo.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-12-23 12:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-23 9:43 Discordant results between UnixBench and nBench Matthieu Olivier
2009-12-23 9:53 ` Avi Kivity
2009-12-23 10:35 ` Matthieu Olivier
2009-12-23 10:37 ` Avi Kivity
2009-12-23 12:27 ` Matthieu Olivier
2009-12-23 12:39 ` Avi Kivity [this message]
2009-12-23 12:55 ` Matthieu Olivier
2009-12-23 12:59 ` Avi Kivity
2009-12-23 13:05 ` Matthieu Olivier
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=4B320F93.6080700@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=ppmarcel@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