From: Rick Jones <rick.jones2@hp.com>
To: Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@intel.com>
Cc: David Miller <davem@davemloft.net>,
"billfink@mindspring.com" <billfink@mindspring.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: netconf notes and materials
Date: Fri, 09 Oct 2009 16:35:06 -0700 [thread overview]
Message-ID: <4ACFC8AA.7010902@hp.com> (raw)
In-Reply-To: <1255129289.8937.39.camel@localhost.localdomain>
Peter P Waskiewicz Jr wrote:
> On Fri, 2009-10-09 at 14:51 -0700, David Miller wrote:
>
>>From: Bill Fink <billfink@mindspring.com>
>>Date: Fri, 9 Oct 2009 17:49:49 -0400
>>
>>
>>>How did you do the NUMA memory performance monitoring that was
>>>presented on one of your slides?
>>
>>Using proprietary internal tools Intel is unlikely to release.
>>
>>On the bright side, some of those metrics will make their way into the
>>'perf' facilities in the kernel so they can be monitored, but not all
>>of them.
>
>
> Yes, they are tools written by our CPU and chipset teams to assist in
> debug. To reinforce what David just said, I know Jesse Barnes is
> working hard with the Intel powers-that-be to get the "approved" public
> PMU counters into the perf utility. I'd imagine the PMU counters for
> IOH memory throughput will be deemed ok, since it's not uncovering any
> IP.
>
> If I hear anything about any of the performance counters, I'll be sure
> to forward that on.
From the standpoint of I/O, anything that might enable a port of:
http://pcitop.berlios.de/
would be goodness.
rick jones
next prev parent reply other threads:[~2009-10-09 23:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-07 11:47 netconf notes and materials David Miller
2009-10-09 21:49 ` Bill Fink
2009-10-09 21:51 ` David Miller
2009-10-09 23:01 ` Peter P Waskiewicz Jr
2009-10-09 23:31 ` Krzysztof Halasa
2009-10-09 23:35 ` Rick Jones [this message]
2010-11-07 19:06 ` Rami Rosen
2010-11-08 1:53 ` David Miller
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=4ACFC8AA.7010902@hp.com \
--to=rick.jones2@hp.com \
--cc=billfink@mindspring.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@intel.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 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.