[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.20.1705222209450.2407@nanos>
Date: Mon, 22 May 2017 22:10:31 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Shivappa Vikas <vikas.shivappa@...el.com>
cc: Vikas Shivappa <vikas.shivappa@...ux.intel.com>,
tony.luck@...el.com, fenghua.yu@...el.com,
ravi.v.shankar@...el.com, eranian@...gle.com, davidcc@...gle.com,
x86@...nel.org, linux-kernel@...r.kernel.org, hpa@...or.com,
peterz@...radead.org
Subject: Re: [PATCH 0/1] x86/cqm: Cqm3 Design Documentation
On Mon, 17 Apr 2017, Shivappa Vikas wrote:
>
> Hello Thomas,
>
> Wanted to know if you had any feedback on the new interface for cqm design
> which is based on monitoring the resctrl groups. It tries to address all the
> requirements discussed in :
>
> https://marc.info/?l=linux-kernel&m=148891934720489
>
> -basically to monitor resctrl groups / per thread including kernel threads.
> -monitor thread from creation (also a child thread forked belongs to same
> group like its parent)
> -monitor subset of tasks in a resctrl group.
> -monitor subset of cpus in a resctrl group.
> -monitor different events (however the first version only shows llc_occupancy)
> -monitor all domains and show per domain data.
>
> I have a patch series but was thinking to send after the design document is
> reviewed so that its easy to review and I can make changes that are discussed
> here.
Send it along. This looks sane. I've wanted to reply long ago, but forgot
about it again. Sorry for the delay.
Thanks,
tglx
Powered by blists - more mailing lists