public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Anton Blanchard <anton@samba.org>,
	Lev Makhlis <mlev@despammed.com>,
	linux-kernel@vger.kernel.org, akpm@zip.com.au
Subject: Re: [RFC] [PATCH] [2.5.35] Run Queue Statistics
Date: Mon, 16 Sep 2002 20:21:12 -0700	[thread overview]
Message-ID: <3D869FA8.7A50BC91@digeo.com> (raw)
In-Reply-To: Pine.LNX.4.44L.0209170007110.1857-100000@imladris.surriel.com

Rik van Riel wrote:
> 
> On Tue, 17 Sep 2002, Anton Blanchard wrote:
> 
> > On a semi related note, vmstat wants to know the number of running,
> > blocked and swapped processes. strace vmstat one day and you will see it
> > currently opens /proc/*/stat (ie one open for each process) just to get
> > these stats.  Yet another place where the monitoring utilities disturb
> > the system way too much.
> >
> > Can we get some things in /proc/stat to give us these numbers? Does
> > "swapped" make any sense on Linux?

Certainly sounds good.  Opening every /proc/<pid>/stat is gross.

> Runnable can be done currently, blocked on IO is trivial once
> Andrew has pushed the iowait stats to Linus.
> 

That'll be a while off yet. I'd like to make sure that we have
all the externally visible changes stable for a week or so,
/proc/diskstats settled down, userspace updated and tested etc.

Just to minimise the disruption and churn which these changes
will cause.

      parent reply	other threads:[~2002-09-17  3:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-16 22:20 [RFC] [PATCH] [2.5.35] Run Queue Statistics Lev Makhlis
2002-09-17  2:59 ` Anton Blanchard
2002-09-17  3:08   ` Rik van Riel
2002-09-17  3:20     ` [despammed] " Lev Makhlis
2002-09-17  3:21     ` Andrew Morton [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=3D869FA8.7A50BC91@digeo.com \
    --to=akpm@digeo.com \
    --cc=akpm@zip.com.au \
    --cc=anton@samba.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mlev@despammed.com \
    --cc=riel@conectiva.com.br \
    /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