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


Groups > linux.kernel > #1647338 > unrolled thread

Re: [PATCH 0/1] x86/cqm: Cqm3 Design Documentation

Started byThomas Gleixner <tglx@linutronix.de>
First post2017-05-22 22:20 +0200
Last post2017-05-22 22:40 +0200
Articles 2 — 2 participants

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.


Contents

  Re: [PATCH 0/1] x86/cqm: Cqm3 Design Documentation Thomas Gleixner <tglx@linutronix.de> - 2017-05-22 22:20 +0200
    Re: [PATCH 0/1] x86/cqm: Cqm3 Design Documentation Shivappa Vikas <vikas.shivappa@intel.com> - 2017-05-22 22:40 +0200

#1647338 — Re: [PATCH 0/1] x86/cqm: Cqm3 Design Documentation

FromThomas Gleixner <tglx@linutronix.de>
Date2017-05-22 22:20 +0200
SubjectRe: [PATCH 0/1] x86/cqm: Cqm3 Design Documentation
Message-ID<tK1Y6-1N3-21@gated-at.bofh.it>
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

[toc] | [next] | [standalone]


#1647356

FromShivappa Vikas <vikas.shivappa@intel.com>
Date2017-05-22 22:40 +0200
Message-ID<tK2hs-1Tl-19@gated-at.bofh.it>
In reply to#1647338

On Mon, 22 May 2017, Thomas Gleixner wrote:

> 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.

Ok - will do , Expecting to send by next week or so..

Thanks,
Vikas

>
> Thanks,
>
> 	tglx
>

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web