public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Karim Yaghmour <karym@info.polymtl.ca>
To: rjwalsh@durables.org
Cc: linux-kernel@vger.rutgers.edu
Subject: Re: kernel profiling
Date: Mon, 26 Jul 1999 15:59:20 -0400	[thread overview]
Message-ID: <379CBE18.B89F1837@info.polymtl.ca> (raw)

On Thu, 8 Jul 1999, Robert Walsh wrote:

> We're currently profiling the kernel NFS daemon (the entire path from
> network to disk) using SPECsfs and other benchmarking mechanisms, and
> before I start working on a home-grown profiling mechanism I'd like to
> make sure I'm not reinventing the wheel.

You might want to check on the tool i've been working on, which enables
you to see exactly what if happening on your system at all times. It
would enable you to see what time is spent in kernel, what time is
spent in the rest of the system, and why.

Moreover, the mechanisms I use are easily extendable. Therefore, if
you find the information given insufficient, you can make the kernel
generate more information without modifying too many things.

You can find the Linux 
Trace Toolkit at the following address :

http://www.info.polymtl.ca/users/karym/www/trace/

The information on how to use it is there and so is some information
on how it works. If you need more info, don't hesitate to contact me
if you need more information.

Of course, it's all under GPL ...

Regards.

==============================================
              Karim Yaghmour
          karym@info.polymtl.ca
            Computer Engineer
      Ecole Polytechnique de Montreal
==============================================

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

             reply	other threads:[~1999-07-26 19:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-26 19:59 Karim Yaghmour [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-08 19:42 KERNEL PROFILING shesha bhushan
2003-04-08 20:03 ` Randy.Dunlap
2003-04-08 20:53   ` Andy Pfiffer
2003-04-08  7:58 shesha bhushan
2003-04-08 15:01 ` Randy.Dunlap
2003-02-06 16:22 kernel profiling Yours Lovingly
2003-02-05 10:56 Yours Lovingly
2003-01-22  0:34 Hui_Ning
2003-01-22 17:07 ` Hanna Linder
     [not found] <3C8E5712.20E5E317@scali.com.suse.lists.linux.kernel>
2002-03-12 21:17 ` Kernel profiling Andi Kleen
2002-03-12 19:29 Steffen Persvold
2002-03-12 21:11 ` John Levon
     [not found] <7m3tm8$7lvnt@fido.engr.sgi.com>
1999-07-09 20:43 ` kernel profiling Dimitris Michailidis

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=379CBE18.B89F1837@info.polymtl.ca \
    --to=karym@info.polymtl.ca \
    --cc=linux-kernel@vger.rutgers.edu \
    --cc=rjwalsh@durables.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