From: Graham Stoney <greyham@research.canon.com.au>
To: Brian Ford <ford@vss.fsi.com>
Cc: Graham Stoney <greyham@research.canon.com.au>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: 2.5 or 2.4 kernel profiling
Date: Tue, 12 Dec 2000 13:36:59 +1100 [thread overview]
Message-ID: <20001212133658.C1773@brixi.research.canon.com.au> (raw)
In-Reply-To: <Pine.GSO.4.21.0012110920300.24199-100000@eos>; from ford@vss.fsi.com on Mon, Dec 11, 2000 at 09:27:18AM -0600
On Mon, Dec 11, 2000 at 09:27:18AM -0600, Brian Ford wrote:
> I agree with you about the profiling stuff. Did you post this idea to the
> main kernel mailing list?
Sure; they were all too busy though. Profiling already worked for most of
them, and a cross-architecture change either requires the co-operation of all
seperate architecture maintainers, or a dictatorial initiative from above.
> Thanks. I had already hacked something like this together. It would be
> great to finalize these and get them into the real sources.
Yes, that would be excellent.
> I also turned checksumming off for testing purposes. It helped some, but
> I think my bottle neck is that I can't get the bus to run faster than 33
> Mhz reliably. If I could get the bus clocked at what it is rated, I might
> be better off.
Absolutely; the bus is the bottleneck. You'll find the network throughput
scales almost linearly with bus speed, so getting it clocked faster will give
a higher payback than more driver tweaking. Also, doesn't the 8260 have
seperate memory subsystems to help get around this?
Regards,
Graham
--
Graham Stoney
Assistant Technology Manager
Canon Information Systems Research Australia
Ph: +61 2 9805 2909 Fax: +61 2 9805 2929
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-12-12 2:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.GSO.4.21.0012071148420.515-100000@eos>
2000-12-07 18:11 ` 2.5 or 2.4 kernel profiling Brian Ford
2000-12-08 17:41 ` diekema_jon
2000-12-08 18:24 ` Brian Ford
2000-12-11 0:45 ` Graham Stoney
2000-12-11 15:27 ` Brian Ford
2000-12-12 2:36 ` Graham Stoney [this message]
2000-12-12 3:26 ` Dan Malek
2000-12-12 7:28 ` Graham Stoney
2000-12-12 16:32 ` Brian Ford
2000-12-12 16:58 ` Dan Malek
2000-12-12 17:17 ` Brian Ford
2000-12-12 21:03 ` Dan Malek
2000-12-13 1:15 ` Graham Stoney
2000-12-13 16:14 ` Dan Malek
2000-12-13 17:23 ` Arto Vuori
2000-12-13 17:33 ` Dan Malek
2000-12-13 17:55 ` Arto Vuori
2000-12-13 22:08 ` Brian Ford
2000-12-13 22:45 ` Jerry Van Baren
2000-12-13 22:53 ` Dan Malek
2000-12-14 17:29 ` FEC/FCC driver issues Brian Ford
2000-12-14 7:21 ` 2.5 or 2.4 kernel profiling Graham Stoney
2000-12-14 16:58 ` Dan Malek
2000-12-15 0:18 ` Graham Stoney
2000-12-12 15:26 ` Brian Ford
2000-12-12 17:12 ` Jerry Van Baren
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=20001212133658.C1773@brixi.research.canon.com.au \
--to=greyham@research.canon.com.au \
--cc=ford@vss.fsi.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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).