Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1576475 > unrolled thread
| Started by | Peter Zijlstra <peterz@infradead.org> |
|---|---|
| First post | 2017-02-08 12:30 +0100 |
| Last post | 2017-02-08 12:30 +0100 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH 00/12] Cqm2: Intel Cache quality monitoring fixes Peter Zijlstra <peterz@infradead.org> - 2017-02-08 12:30 +0100
| From | Peter Zijlstra <peterz@infradead.org> |
|---|---|
| Date | 2017-02-08 12:30 +0100 |
| Subject | Re: [PATCH 00/12] Cqm2: Intel Cache quality monitoring fixes |
| Message-ID | <t8yBH-88n-19@gated-at.bofh.it> |
On Fri, Jan 20, 2017 at 12:11:53PM -0800, David Carrillo-Cisneros wrote: > Implementation ideas: > > First idea is to expose one monitoring file per resource in a CTRLGRP, > so the list of CTRLGRP's files would be: schemata, tasks, cpus, > monitor_l3_0, monitor_l3_1, ... > > the monitor_<resource_id> file descriptor is passed to perf_event_open > in the way cgroup file descriptors are passed now. All events to the > same (CTRLGRP,resource_id) share RMID. > > The RMID allocation part can either be handled by RDT Allocation or by > the RDT Monitoring PMU. Either ways, the existence of PMU's > perf_events allocates/releases the RMID. So I've had complaints about exactly that behaviour. Someone wanted RMIDs assigned (and start measuring) the moment the grouping got created/tasks started running etc.. So I think the design should also explicitly state how this is supposed to be handled and not left as an implementation detail.
Back to top | Article view | linux.kernel
csiph-web