linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Bill Fink <billfink@mindspring.com>
To: <acurtis@onz.com>
Cc: linuxppc-dev@lists.linuxppc.org, Bill Fink <billfink@mindspring.com>
Subject: Re: Debugging Network Performance
Date: Wed, 5 Jun 2002 09:56:31 -0400	[thread overview]
Message-ID: <20020605095631.6f8a03e3.billfink@mindspring.com> (raw)
In-Reply-To: <NCBBIINEHIPFGJPLBEIFMECIDIAA.acurtis@onz.com>


On Wed, 5 Jun 2002, "Allen Curtis" wrote:

> >     "It would be interesting to see where the cpu is being used. Could you
> >     boot with profile=2 and use readprofile to find the worst cpu hogs
> >     during a run?"
>
> Where can I find documentation on the profile=## option? Are there also
> tools that will help to interpret the logs?

Since I didn't actually try it, I don't have a lot more information.
>From /usr/src/linux/Documentation/kernel-parameters.txt:

        profile=        [KNL] enable kernel profiling via /proc/profile
                        (param:log level).

And of course check the readprofile man page.

						-Bill

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-06-05 13:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-05  5:18 Debugging Network Performance Bill Fink
2002-06-05 13:16 ` Allen Curtis
2002-06-05 13:56   ` Bill Fink [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-06-05 12:18 Jean-Denis Boyer
2002-06-05 13:35 ` Allen Curtis
2002-06-04 14:35 Mark Wisner
2002-06-04 14:46 ` Allen Curtis
2002-06-04 15:05   ` Michael Fischer
2002-06-04 11:12 Mark Wisner
2002-06-04 13:30 ` Allen Curtis
2002-06-04  4:34 Allen Curtis
2002-06-04  9:50 ` Kenneth Johansson
2002-06-04  3:27 Allen Curtis

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=20020605095631.6f8a03e3.billfink@mindspring.com \
    --to=billfink@mindspring.com \
    --cc=acurtis@onz.com \
    --cc=linuxppc-dev@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).