From: Krzysztof Halasa <khc@pm•waw.pl>
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: Sat, 10 Oct 2009 01:31:44 +0200 [thread overview]
Message-ID: <m363aof8kf.fsf@intrepid.localdomain> (raw)
In-Reply-To: <1255129289.8937.39.camel@localhost.localdomain> (Peter P. Waskiewicz, Jr.'s message of "Fri, 09 Oct 2009 16:01:29 -0700")
Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@intel•com> writes:
> 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.
Ehm perhaps something similar could also happen to source of IXP4xx
microcode and/or NPE docs? Not sure about IP, though isn't any IP there
already patented (and thus available)?
This is especially needed WRT HSS (sync serial port).
:-)
--
Krzysztof Halasa
next prev parent reply other threads:[~2009-10-09 23:32 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 [this message]
2009-10-09 23:35 ` Rick Jones
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=m363aof8kf.fsf@intrepid.localdomain \
--to=khc@pm$(echo .)waw.pl \
--cc=billfink@mindspring$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=netdev@vger$(echo .)kernel.org \
--cc=peter.p.waskiewicz.jr@intel$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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