From: Thomas Gleixner <tglx@linutronix.de>
To: Shivappa Vikas <vikas.shivappa@intel.com>
Cc: Vikas Shivappa <vikas.shivappa@linux.intel.com>,
tony.luck@intel.com, fenghua.yu@intel.com,
ravi.v.shankar@intel.com, eranian@google.com, davidcc@google.com,
x86@kernel.org, linux-kernel@vger.kernel.org, hpa@zytor.com,
peterz@infradead.org
Subject: Re: [PATCH 0/1] x86/cqm: Cqm3 Design Documentation
Date: Mon, 22 May 2017 22:10:31 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1705222209450.2407@nanos> (raw)
In-Reply-To: <alpine.DEB.2.10.1704171611540.3411@vshiva-Udesk>
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
next prev parent reply other threads:[~2017-05-22 20:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 0:02 Vikas Shivappa
2017-04-04 0:02 ` [PATCH 1/1] x86/cqm: Cqm3 Documentation Vikas Shivappa
2017-04-17 23:18 ` [PATCH 0/1] x86/cqm: Cqm3 Design Documentation Shivappa Vikas
2017-05-22 20:10 ` Thomas Gleixner [this message]
2017-05-22 20:34 ` Shivappa Vikas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.20.1705222209450.2407@nanos \
--to=tglx@linutronix.de \
--cc=davidcc@google.com \
--cc=eranian@google.com \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=ravi.v.shankar@intel.com \
--cc=tony.luck@intel.com \
--cc=vikas.shivappa@intel.com \
--cc=vikas.shivappa@linux.intel.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®