From: Peter Zijlstra <peterz@infradead.org>
To: "Fredrik Markström" <fredrik.markstrom@gmail.com>
Cc: mingo@redhat.com, linux-kernel@vger.kernel.org,
"Rik van Riel" <riel@redhat.com>, "Jason Low" <jason.low2@hp.com>,
"Frédéric Weisbecker" <fweisbec@gmail.com>
Subject: Re: [PATCH 1/1] cputime: Make the reported utime+stime correspond to the actual runtime.
Date: Thu, 2 Jul 2015 14:11:26 +0200 [thread overview]
Message-ID: <20150702121126.GP3644@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <CAKdL+dTTgfKrskE5d6OxktxJ4SHeMvmRPka4oAQ97LJmDefn6A@mail.gmail.com>
On Tue, Jun 30, 2015 at 08:30:05PM +0200, Fredrik Markström wrote:
> But I don't think the "wobblies" in the division is, since the division doesn't
> affect the sum (prev->stime + prev->rtime) anymore, so that comment should
> go, right ?
Agreed.
> Well I guess it can be a problem on a system where 120 cores are doing nothing
> but hammering on rusage... on the other hand I feel a system like that
> deserves it. :)
True, doing stupid deserves stupid, but somehow people often tend to
disagree with it when its them doing it :-)
Imagine someone doing a gprof like thing where they stuff a getrusage()
call in the mcount hook and then run their many threaded application.
Provided they use RUSAGE_THREAD it doesn't even sound too insane..
next prev parent reply other threads:[~2015-07-02 12:11 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-12 8:55 [PATCH 0/1] cputime: Make the reported utime+stime correspond to the actual runtime Fredrik Markstrom
2015-06-12 8:55 ` [PATCH 1/1] " Fredrik Markstrom
2015-06-12 10:16 ` Peter Zijlstra
2015-06-12 11:01 ` Peter Zijlstra
2015-06-15 15:34 ` Fredrik Markström
2015-06-16 14:35 ` Fredrik Markström
2015-06-29 14:58 ` Peter Zijlstra
2015-06-29 15:28 ` Fredrik Markström
2015-06-29 18:54 ` Jason Low
2015-06-29 19:08 ` Fredrik Markström
2015-06-29 22:11 ` Jason Low
2015-06-30 9:30 ` Peter Zijlstra
2015-06-30 11:50 ` Fredrik Markström
2015-06-30 12:18 ` Peter Zijlstra
2015-06-30 18:30 ` Fredrik Markström
2015-07-02 12:11 ` Peter Zijlstra [this message]
2015-07-02 13:07 ` Peter Zijlstra
2015-07-07 0:51 ` Frederic Weisbecker
2015-07-07 7:59 ` Peter Zijlstra
2015-07-07 8:09 ` Peter Zijlstra
2015-07-07 12:10 ` Fredrik Markström
2015-07-07 15:37 ` Peter Zijlstra
2015-07-07 13:34 ` Frederic Weisbecker
2015-07-07 15:34 ` Peter Zijlstra
2015-07-07 16:26 ` Frederic Weisbecker
2015-06-13 11:17 ` Fredrik Markström
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=20150702121126.GP3644@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=fredrik.markstrom@gmail.com \
--cc=fweisbec@gmail.com \
--cc=jason.low2@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=riel@redhat.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