public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Seigh <jseigh_02@xemaps.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Cpu utilization per thread
Date: Wed, 22 Jun 2005 13:41:48 -0400	[thread overview]
Message-ID: <d9c7dt$9dk$1@sea.gmane.org> (raw)
In-Reply-To: <07f701c5765f$cd437cd0$99bcc68a@blr.st.com>

N Chandra Shekhar REDDY wrote:
> Hi all,
> Can any body tell me 
> How to find cpu utilization per thread excluding wait times and sleep times?
> Regards
> ncs
> 

man 5 proc

The thread stuff is in the /proc/<pid>/tasks subdirectory but I think
the status is process specific not thread specific.

--
Joe Seigh


  parent reply	other threads:[~2005-06-22 17:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-21 12:50 Cpu utilization per thread N Chandra Shekhar REDDY
2005-06-22  1:31 ` J.A. Magallon
2005-06-23  6:18   ` N Chandra Shekhar REDDY
2005-06-22 17:41 ` Joe Seigh [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-06-21  6:31 N Chandra Shekhar REDDY
2005-06-21  5:29 CPU " N Chandra Shekhar REDDY

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='d9c7dt$9dk$1@sea.gmane.org' \
    --to=jseigh_02@xemaps.com \
    --cc=linux-kernel@vger.kernel.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