From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] dubious process system time.
Date: Thu, 24 Aug 2006 18:02:43 +0200 [thread overview]
Message-ID: <1156435363.28464.33.camel@localhost> (raw)
In-Reply-To: <200608241718.29406.ak@suse.de>
On Thu, 2006-08-24 at 17:18 +0200, Andi Kleen wrote:
> > At the moment hardirq+softirq is just added to a random process, in
> > general this is completely wrong.
>
> It's better than not accounting it at all.
I think it is worse than not accounting it. You are "charging" a process
of some user for something that the user has nothing to do with.
> > You just need a system with a cpu hog
> > and an i/o bound process and you get queer results.
>
> Yes, but system load that is invisible to standard monitoring
> tools is even worse.
But it isn't invisible. cpustat->hardirq and cpustate->softirq will be
increased. /proc/stat will show the system time spent in these two
contexts.
> If you stop accounting it to random processes you have to
> account it somewhere else. Preferably somewhere that standard tools
> automatically pick up.
Again, why do I have to account non-process related time to a process?
Ihmo that is completly wrong.
--
blue skies,
Martin.
Martin Schwidefsky
Linux for zSeries Development & Services
IBM Deutschland Entwicklung GmbH
"Reality continues to ruin my life." - Calvin.
next prev parent reply other threads:[~2006-08-24 16:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-24 12:18 [patch] dubious process system time Martin Schwidefsky
2006-08-24 12:32 ` Andi Kleen
2006-08-24 13:28 ` Martin Schwidefsky
2006-08-24 15:18 ` Andi Kleen
2006-08-24 16:02 ` Martin Schwidefsky [this message]
2006-08-25 10:12 ` Helge Hafting
2006-08-25 10:29 ` Martin Schwidefsky
2006-08-25 12:58 ` Paul Mackerras
2006-08-24 23:40 ` Paul Mackerras
2006-08-25 8:18 ` Martin Schwidefsky
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=1156435363.28464.33.camel@localhost \
--to=schwidefsky@de.ibm.com \
--cc=ak@suse.de \
--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 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.