Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1576475

Re: [PATCH 00/12] Cqm2: Intel Cache quality monitoring fixes

From Peter Zijlstra <peterz@infradead.org>
Newsgroups linux.kernel
Subject Re: [PATCH 00/12] Cqm2: Intel Cache quality monitoring fixes
Date 2017-02-08 12:30 +0100
Message-ID <t8yBH-88n-19@gated-at.bofh.it> (permalink)
References <t0Ug1-1O0-11@gated-at.bofh.it> <t1xho-1jm-5@gated-at.bofh.it> <t1Ch4-4tl-23@gated-at.bofh.it> <t1IFQ-8tF-21@gated-at.bofh.it> <t1NPc-3oi-15@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


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 linux.kernel | Previous | Next | Find similar | Unroll thread


Thread

Re: [PATCH 00/12] Cqm2: Intel Cache quality monitoring fixes Peter Zijlstra <peterz@infradead.org> - 2017-02-08 12:30 +0100

csiph-web