public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Anders Fugmann <afu@fugmann.dhs.org>
To: linux-kernel@vger.kernel.org
Subject: Process info
Date: Tue, 02 Apr 2002 11:21:15 +0200	[thread overview]
Message-ID: <3CA9780B.7040900@fugmann.dhs.org> (raw)

Hi.

Is it possible to obtain per process statistics in linux 2.4/2.5?
e.g. #ticks the process is assigned to a PE (Processing element), #ticks 
  suspended (blocked) state, #ticks on runqueue? etc.

The reason for me asking is that I want to simulate some load-cases on 
Linux, and therefore need some real data on how process on behaves.
(How much CPU-time does it want/need, How often does the process suspend 
itself and for how long, etc.)

Anyone out there who as information on this. I was hoping to simulate a 
gcc process. Then add 200 of them, and see how my small simulator 
behaves, and compare this to how things are actually working in Linux.
(the old `make bzImage -j 200` test.)

Regards
Anders Fugmann










                 reply	other threads:[~2002-04-02  9:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3CA9780B.7040900@fugmann.dhs.org \
    --to=afu@fugmann.dhs.org \
    --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