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: Thu, 22 Jul 2010 19:12:30 -0700 From: Venkatesh Pallipadi <venki@...gle.com> To: Martin Schwidefsky <schwidefsky@...ibm.com> Cc: Peter Zijlstra <peterz@...radead.org>, Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>, Thomas Gleixner <tglx@...utronix.de>, Balbir Singh <balbir@...ux.vnet.ibm.com>, Paul Menage <menage@...gle.com>, linux-kernel@...r.kernel.org, Paul Turner <pjt@...gle.com>, Heiko Carstens <heiko.carstens@...ibm.com>, Paul Mackerras <paulus@...ba.org>, Tony Luck <tony.luck@...el.com> Subject: Re: [PATCH 0/4] Finer granularity and task/cgroup irq time accounting On Thu, Jul 22, 2010 at 4:12 AM, Martin Schwidefsky <schwidefsky@...ibm.com> wrote: > On Tue, 20 Jul 2010 09:55:29 -0700 > Venkatesh Pallipadi <venki@...gle.com> wrote: > <snip> > >> Archs like s390/powerpc/ia64 already do this kind of accounting with >> VIRT_CPU_ACCOUNTING. So, this patch will give them task and cgroup >> level info free of charge (other than potential bugs with this code >> change :-)). > > Well, the task and cgroup information is there but what does it really > tell me? As long as the irq & softirq time can be caused by any other > process I don't see the value of this incorrect data point. > Data point will be correct. How it gets used is a different qn. This interface will be useful for Alert/Paranoid/Annoyed user/admin who sees that the job exec_time is high but it is not doing any useful work. With this additional info, he can probably choose to move the job off to different system. User probably knows more about the job characteristics and whether it is rightly or wrongly being charged. Say one task in the task group being charged for another task in the task group is probably OK as well. So, user can look at this in different granularity than kernel can. Thanks, Venki -- 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