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:	Tue, 08 Feb 2011 10:21:05 +0100
From:	Peter Zijlstra <>
To:	Chris Friesen <>
Cc:	Ingo Molnar <>,
	Linux Kernel Mailing List <>
Subject: Re: RFC: /proc/<pid>/sched should contain cumulative data for all
 threads in process

On Mon, 2011-02-07 at 16:29 -0600, Chris Friesen wrote:
> Hi,
> We've got a tool that gathers lots of scheduling data for each process
> (not task/thread) on the system.
> For /proc/<pid>/{stat,io} this is straightforward, as the per-thread
> values are summed together for the process as a whole.
> However, /proc/<pid>/sched only shows the data for the individual thread
> with the same tid as the pid.  To get a per-process view we need to
> manually scan all the threads and sum them--and this can get expensive
> due to all the extra file operations, parsing, etc.
> Was this a concious design decision, or just an oversight?  Would a
> patch converting it to whole-process values be accepted or is it enough
> of a standard interface that we can't break existing apps that expect
> the current behaviour?

I'd as soon remove all that stuff than extend it, its an abi liability,
esp since you're talking about tools parsing this stuff.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists