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
| ||
|
Date: Fri, 19 Nov 2010 20:46:25 +0100 From: Michael Holzheu <holzheu@...ux.vnet.ibm.com> To: Oleg Nesterov <oleg@...hat.com> Cc: Shailabh Nagar <nagar1234@...ibm.com>, Andrew Morton <akpm@...ux-foundation.org>, Venkatesh Pallipadi <venki@...gle.com>, Suresh Siddha <suresh.b.siddha@...el.com>, Peter Zijlstra <a.p.zijlstra@...llo.nl>, Ingo Molnar <mingo@...e.hu>, John stultz <johnstul@...ibm.com>, Thomas Gleixner <tglx@...utronix.de>, Balbir Singh <balbir@...ux.vnet.ibm.com>, Martin Schwidefsky <schwidefsky@...ibm.com>, Heiko Carstens <heiko.carstens@...ibm.com>, Roland McGrath <roland@...hat.com>, linux-kernel@...r.kernel.org, linux-s390@...r.kernel.org Subject: Re: [RFC][PATCH v2 5/7] taskstats: Improve cumulative CPU time accounting Hello Oleg, On Thu, 2010-11-18 at 18:10 +0100, Oleg Nesterov wrote: > > 2. Because of reparent to init, there are situations where it is > > not clear to which tasks the CPU time of dead tasks between > > two snapshots has been accounted. This is a problem for example 2. > > Yes, I see. > > But I must admit, _personally_ I am not sure this problem worth the > trouble. I think you are right... For that function, the introduced overhead, additional code and especially the possible confusion with two process hierarchies is not worth the effort. Maybe we have a chance to solve the reparent problem by introducing task exit event filters (e.g. give me all exit events for processes that have init as parent). So I will send no more patches with the parallel hierarchy: Good news for you :-) But for the second problem with the forgotten CPU time, I would like send you a new patch set, separated as you have requested. Although I personally think that also there we probably have no good chances to get them accepted upstream, because the signal_struct size is increased and some cycles are added to the task exit processing. It would be nice, if you find some time to look at the patches, but no hurry! Michael -- 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/
Powered by blists - more mailing lists