From: Andi Kleen <andi@firstfloor.org>
To: Luke Gorrie <luke@snabb.co>
Cc: Andi Kleen <andi@firstfloor.org>, linux-perf-users@vger.kernel.org
Subject: Re: First time user, problem with toplev.py levels (-l)
Date: Wed, 25 Sep 2013 17:54:16 +0200 [thread overview]
Message-ID: <20130925155416.GJ18242@two.firstfloor.org> (raw)
In-Reply-To: <CAA2XHbfK5qkf6UERFu_zLK5NEA+ZSs3=2QCeZ3MvkSceY9bxqg@mail.gmail.com>
On Wed, Sep 25, 2013 at 05:29:49PM +0200, Luke Gorrie wrote:
> On 25 September 2013 17:24, Andi Kleen <andi@firstfloor.org> wrote:
> > What CPU do you have (head -n20 /proc/cpuinfo) ?
>
> $ head -n20 /proc/cpuinfo
> processor : 0
> vendor_id : GenuineIntel
> cpu family : 6
> model : 45
> model name : Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHz
toplev doesn't have a detailed model for SandyBridge-E currently,
that is why only level 1 is enabled.
You could force snb in the code for jkt (the table at line 175+), but some
of the estimated latencies would be a bit off and it would not
support NUMA.
-Andi
next prev parent reply other threads:[~2013-09-25 15:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 11:44 First time user, problem with toplev.py levels (-l) Luke Gorrie
2013-09-25 15:24 ` Andi Kleen
2013-09-25 15:29 ` Luke Gorrie
2013-09-25 15:54 ` Andi Kleen [this message]
2013-09-25 17:18 ` Luke Gorrie
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=20130925155416.GJ18242@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=luke@snabb.co \
/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