All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@turbolabs.com>
To: Sven Heinicke <sven@research.nj.nec.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: /proc/stat description for proc.txt
Date: Thu, 15 Nov 2001 11:59:39 -0700	[thread overview]
Message-ID: <20011115115939.I5739@lynx.no> (raw)
In-Reply-To: <15347.57175.887835.525156@abasin.nj.nec.com>
In-Reply-To: <15347.57175.887835.525156@abasin.nj.nec.com>; from sven@research.nj.nec.com on Thu, Nov 15, 2001 at 10:29:27AM -0500

On Nov 15, 2001  10:29 -0500, Sven Heinicke wrote:
> +cpu  58903 1 7337 221340
> +
> +The individual "cpu" entry is will be the same as "cpu0" if you only
> +have one CPU on your system.  Otherwise the "cpu" entry will be a
> +total of all the separate CPU stats.  The four numbers following "cpu"
> +entries are: user, nice, system and unused usage (I think unused usage
> +anyway).

Units of what?  Probably jiffies.  Also "unused" is actually better
described as "idle".

> +disk_io: (3,0):(21459,9839,195208,11620,184240) 
> +
> +The "disk_io" shows data for each active disk.  The above example only
> +shows one active disk.  The first pair is the major followed by the
> +disk number entry.  The others are `dk_drive', `dk_drive_rio',
> +`dk_drive_rblk', `dk_drive_wio', `dk_drive_wblk' entries for that
> +disk.  (If I ever figure out what they are i'll describe them
> +beter. -Sven)

Looks like (in order):
- total number of I/O operations on this drive
- read I/O operations
- read I/O sectors
- write I/O operations
- write I/O sectors

> +btime 1005238271
> +Can't figure what "btime" is.

This appears to be the time in seconds (i.e. unix time = seconds
since Jan 1, 1970), when the system booted. time(0) - btime will
give you uptime in seconds, (as should the sum of all the "cpu"
times / HZ, if you knew what HZ was in userspace).

Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/


  reply	other threads:[~2001-11-15 19:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-15 15:29 /proc/stat description for proc.txt Sven Heinicke
2001-11-15 18:59 ` Andreas Dilger [this message]
2001-11-15 20:18   ` Sven Heinicke
2001-11-15 20:37     ` Andreas Dilger
2001-11-15 20:43       ` Sven Heinicke
2001-11-15 21:00         ` Andreas Schwab
2001-11-15 21:10           ` Sven Heinicke
2001-11-15 21:51             ` Marius Gedminas
2001-11-16 16:50   ` Anthony DeRobertis
2001-11-20 23:02 ` Jorge Nerin
2001-11-21 15:47   ` Sven Heinicke

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=20011115115939.I5739@lynx.no \
    --to=adilger@turbolabs.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sven@research.nj.nec.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.