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: Wed, 1 Feb 2017 17:12:41 -0800 From: David Carrillo-Cisneros <davidcc@...gle.com> To: Andi Kleen <andi@...stfloor.org> Cc: "Luck, Tony" <tony.luck@...el.com>, Thomas Gleixner <tglx@...utronix.de>, Vikas Shivappa <vikas.shivappa@...ux.intel.com>, "Shivappa, Vikas" <vikas.shivappa@...el.com>, Stephane Eranian <eranian@...gle.com>, linux-kernel <linux-kernel@...r.kernel.org>, x86 <x86@...nel.org>, "hpa@...or.com" <hpa@...or.com>, Ingo Molnar <mingo@...nel.org>, Peter Zijlstra <peterz@...radead.org>, "Shankar, Ravi V" <ravi.v.shankar@...el.com>, "Yu, Fenghua" <fenghua.yu@...el.com>, "Kleen, Andi" <andi.kleen@...el.com>, "Anvin, H Peter" <h.peter.anvin@...el.com> Subject: Re: [PATCH 00/12] Cqm2: Intel Cache quality monitoring fixes On Wed, Feb 1, 2017 at 4:35 PM, Andi Kleen <andi@...stfloor.org> wrote: > "Luck, Tony" <tony.luck@...el.com> writes: >> 9) Measure per logical CPU (pick active RMID in same precedence for task/cpu as CAT picks CLOSID) >> 10) Put multiple CPUs into a group > > I'm not sure this is a real requirement. It's just an optimization, > right? If you can assign policies to threads, you can implicitly set it > per CPU through affinity (or the other way around). That's difficult when distinct users/systems do monitoring and system management. What if the cluster manager decides to change affinity for a task after the monitoring service has initiated monitoring a CPU in the way you describe? > The only benefit would be possibly less context switch overhead, > but if all the thread (including idle) assigned to a CPU have the > same policy it would have the same results. I think another of the reasons for the CPU monitoring requirement is to monitor interruptions in CPUs running the idle thread. In CAT, those interruptions use the CPU's CLOSID. Here they'd use the CPU's RMID. Since RMID's are scarce, CPUs can be aggregated into groups to save many. Also, if perf's like monitoring is supported, it'd allow something like perf stat -e LLC-load,LLC-prefetches,intel_cqm/total_bytes -C 2 Thanks, David
Powered by blists - more mailing lists