linux-kernel - Re: 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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110208151434.GA20357@elte.hu>
Date:	Tue, 8 Feb 2011 16:14:34 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Chris Friesen <chris.friesen@...band.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: RFC: /proc/<pid>/sched should contain cumulative data for all
 threads in process


* Peter Zijlstra <peterz@...radead.org> wrote:

> Very much depends on what is wanted, but most of the stuff inside those files is 
> very specific to the implementation and pinning any of that to an ABI is like 
> silly.

Why? If the implementation changes then those values lose meaning and the most 
correct value to report is *zero* and that's it.

That's how such things were always done, it was never a problem in the past 15 
years. Why should it start being a problem suddenly?

Thanks,

	Ingo
--
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/