All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Helge Hafting <helge.hafting@aitel.hist.no>
Cc: Andi Kleen <ak@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: [patch] dubious process system time.
Date: Fri, 25 Aug 2006 12:29:28 +0200	[thread overview]
Message-ID: <1156501768.1640.19.camel@localhost> (raw)
In-Reply-To: <44EECCF9.7080902@aitel.hist.no>

On Fri, 2006-08-25 at 12:12 +0200, Helge Hafting wrote:
> > Again, why do I have to account non-process related time to a process?
> > Ihmo that is completly wrong.
> >   
> If softirq time have to be accounted to a process (so as to not
> get lost), how about accounting it to the softirqd process?  Much
> more reasonable than random processes.

The main question still is if it is correct to add softirq/hardirq time
to the system time of a process. If the answer turns out to be yes, then
it might be a clever idea to account softirq time to the softirqd. That
still leaves the question what to do with hardirq time ..
My take still is that softirq/hardirq time does not belong to the system
time of any process.

-- 
blue skies,
  Martin.

Martin Schwidefsky
Linux for zSeries Development & Services
IBM Deutschland Entwicklung GmbH

"Reality continues to ruin my life." - Calvin.



  reply	other threads:[~2006-08-25 10:29 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
2006-08-25 10:12         ` Helge Hafting
2006-08-25 10:29           ` Martin Schwidefsky [this message]
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=1156501768.1640.19.camel@localhost \
    --to=schwidefsky@de.ibm.com \
    --cc=ak@suse.de \
    --cc=helge.hafting@aitel.hist.no \
    --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.