linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rik van Riel <riel@conectiva.com.br>
To: Andrew Morton <akpm@digeo.com>
Cc: Rick Lindsley <ricklind@us.ibm.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH] sard changes for 2.5.34
Date: Thu, 12 Sep 2002 17:38:27 -0300 (BRT)	[thread overview]
Message-ID: <Pine.LNX.4.44L.0209121734190.1857-100000@imladris.surriel.com> (raw)
In-Reply-To: <3D80EE1D.34AF4FF2@digeo.com>

On Thu, 12 Sep 2002, Andrew Morton wrote:

> Looks like we can take the disk stats out of kernel_stat, move all
> the vm-related things out of kernel_stat into struct page_state and
> what's left of kernel_stat?
>
>         unsigned int per_cpu_user[NR_CPUS],
>                      per_cpu_nice[NR_CPUS],
>                      per_cpu_system[NR_CPUS];

[ insert idle and iowait stats here ;) ]

>         unsigned int irqs[NR_CPUS][NR_IRQS];
>
> And that's good, because "kernel statistics" was clearly too
> broad a concept.  The above is just one concept: interrupts and
> scheduler things.

Absolutely agreed, this makes things much more manageable.

Btw, how about accounting for the number of syscalls made,
like some other Unix systems do ? ;)

> I'm not sure that I want to add 14 more fields to /proc/meminfo.
> So a new /proc/vmstat may appear.  We would then have:
>
> /proc/stat		scheduler things
> /proc/diskstat		disk things
> /proc/vmstat		vm things

Sounds fair, current procps doesn't support the new /proc/stat
fields anyway. Let me know what stuff will look like and I'll
get procps into gear.

regards,

Rik
-- 
Bravely reimplemented by the knights who say "NIH".

http://www.surriel.com/		http://distro.conectiva.com/

Spamtraps of the month:  september@surriel.com trac@trac.org


  reply	other threads:[~2002-09-12 20:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-12  2:10 [RFC][PATCH] sard changes for 2.5.34 Rick Lindsley
2002-09-12  2:42 ` Andrew Morton
2002-09-12  2:50   ` Rik van Riel
2002-09-12  6:40   ` Rick Lindsley
2002-09-12  7:20     ` Andrew Morton
2002-09-12  9:18       ` Rick Lindsley
2002-09-12 10:01         ` Alexander Viro
2002-09-12 10:33           ` Rick Lindsley
2002-09-12 19:42         ` Andrew Morton
2002-09-12 20:38           ` Rik van Riel [this message]
2002-09-12 16:16       ` Rik van Riel
2002-09-12 16:48         ` Andrew Morton
2002-09-12 23:32       ` Denis Vlasenko
2002-09-12 18:49         ` Andrew Morton
2002-09-12 19:50           ` Rick Lindsley
2002-09-13 11:39 Dipankar Sarma
2002-09-14 18:57 Lev Makhlis
2002-09-18 17:54 ` Randy.Dunlap
2002-09-18 19:43   ` Lev Makhlis

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=Pine.LNX.4.44L.0209121734190.1857-100000@imladris.surriel.com \
    --to=riel@conectiva.com.br \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ricklind@us.ibm.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;
as well as URLs for NNTP newsgroup(s).