linux-kernel - Re: [PATCH 1/1] cputime: Make the reported utime+stime correspond to the actual runtime.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 2 Jul 2015 14:11:26 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Fredrik Markström <fredrik.markstrom@...il.com>
Cc:	mingo@...hat.com, linux-kernel@...r.kernel.org,
	Rik van Riel <riel@...hat.com>,
	Jason Low <jason.low2@...com>,
	Frédéric Weisbecker <fweisbec@...il.com>
Subject: Re: [PATCH 1/1] cputime: Make the reported utime+stime correspond to
 the actual runtime.

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..
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/