linux-kernel - RFC: /proc/<pid>/sched should contain cumulative data for all threads in process

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-next>] [day] [month] [year] [list]

Message-ID: <4D50723B.7020400@genband.com>
Date:	Mon, 07 Feb 2011 16:29:15 -0600
From:	Chris Friesen <chris.friesen@...band.com>
To:	Ingo Molnar <mingo@...e.hu>, Peter Zijlstra <peterz@...radead.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: RFC: /proc/<pid>/sched should contain cumulative data for all threads
 in process

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?

Thanks,
Chris

-- 
Chris Friesen
Software Developer
GENBAND
chris.friesen@...band.com
www.genband.com
--
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/