mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-390@vm.marist.edu,
	arjanv@redhat.com, tim.bird@am.sony.com, mulix@mulix.org,
	alan@redhat.com, crisw@osdl.org, jan.glauber@de.ibm.com
Subject: Re: [PATCH] timer (6/6): add cpu steal time fields to procps.
Date: Wed, 18 Aug 2004 15:18:39 +0200	[thread overview]
Message-ID: <20040818131839.GI467@openzaurus.ucw.cz> (raw)
In-Reply-To: <20040805180557.GG9240@mschwid3.boeblingen.de.ibm.com>

Hi!

> [PATCH] timer (6/6): add cpu steal time fields to procps.
> 
> From: Martin Schwidefsky <schwidefsky@de.ibm.com>
> 
> Make use of the cpu steal time field in /proc/stat that has been
> introduces by the cputime patch. The new output of top looks like
> this:
> 
> top - 09:50:20 up 11 min,  3 users,  load average: 8.94, 7.17, 3.82
> Tasks:  78 total,   8 running,  70 sleeping,   0 stopped,   0 zombie
>  Cpu0 : 38.7%us,  4.2%sy,  0.0%ni,  0.0%id,  2.4%wa,  1.8%hi,  0.0%si, 53.0%st
>  Cpu1 : 38.5%us,  0.6%sy,  0.0%ni,  5.1%id,  1.3%wa,  1.9%hi,  0.0%si, 52.6%st
>  Cpu2 : 54.0%us,  0.6%sy,  0.0%ni,  0.6%id,  4.9%wa,  1.2%hi,  0.0%si, 38.7%st
>  Cpu3 : 49.1%us,  0.6%sy,  0.0%ni,  1.2%id,  0.0%wa,  0.0%hi,  0.0%si, 49.1%st
>  Cpu4 : 35.9%us,  1.2%sy,  0.0%ni, 15.0%id,  0.6%wa,  1.8%hi,  0.0%si, 45.5%s
>  Cpu5 : 43.0%us,  2.1%sy,  0.7%ni,  0.0%id,  4.2%wa,  1.4%hi,  0.0%si, 48.6%st
> Mem:    251832k total,   155448k used,    96384k free,     1212k buffers
> Swap:   524248k total,    17716k used,   506532k free,    18096k cached



You really need to write nice description into Documentation describing what cpu steal
time is. Will it be always 0 on  non-virtualized machines?
What about hyperthreading?



-- 
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms         


      reply	other threads:[~2004-08-21 20:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-05 18:05 Martin Schwidefsky
2004-08-18 13:18 ` Pavel Machek [this message]

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=20040818131839.GI467@openzaurus.ucw.cz \
    --to=pavel@suse.cz \
    --cc=alan@redhat.com \
    --cc=arjanv@redhat.com \
    --cc=crisw@osdl.org \
    --cc=jan.glauber@de.ibm.com \
    --cc=linux-390@vm.marist.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mulix@mulix.org \
    --cc=schwidefsky@de.ibm.com \
    --cc=tim.bird@am.sony.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®