From: Ingo Molnar <mingo@kernel.org>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Vikas Shivappa <vikas.shivappa@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Shivappa, Vikas" <vikas.shivappa@intel.com>,
"Fleming, Matt" <matt.fleming@intel.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"tj@kernel.org" <tj@kernel.org>,
"Auld, Will" <will.auld@intel.com>,
"Hansen, Dave" <dave.hansen@intel.com>,
"Kleen, Andi" <andi.kleen@intel.com>,
"Juvva, Kanaka D" <kanaka.d.juvva@intel.com>
Subject: Re: [PATCH V4 0/7] x86/intel_rdt: Intel Cache Allocation Technology
Date: Thu, 26 Feb 2015 12:37:39 +0100 [thread overview]
Message-ID: <20150226113739.GB4191@gmail.com> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F329ED336@ORSMSX114.amr.corp.intel.com>
* Luck, Tony <tony.luck@intel.com> wrote:
> > The CAT thing was annoying already, but at least one
> > can find that in the SDM, this RDT thing, not a single
> > mention.
>
> The problems of development at the bleeding edge. Would
> you rather Linux sat on the sidelines until there are
> enough Google hits from other users of new features?
Well, we'd prefer there to be A) published documentation,
or, lacking published documentation, there be B) a coherent
technical description within the code itself what the
purpose is and how it all works conceptually (minus the
buzzwords), so that we have a common starting point when
reviewing it.
> Technology: Intel Resource Director Technology
>
> Description: Allows the hypervisor to monitor Last Level Cache usage at the application
> and VM levels.
>
> Benefit: Helps to improve performance and efficiency by providing better
> information for scheduling, load balancing, and workload migration
>
> Which isn't any help in evaluating this patch series :-(
No, but it already tells us more than the 0/7 description
of the patch series did! It should be possible to improve
on that.
Maintainers reverse engineering the implementation is an
inefficient approach.
Thanks,
Ingo
next prev parent reply other threads:[~2015-02-26 11:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 23:16 [PATCH V4 0/7] x86/intel_rdt: Intel Cache Allocation Technology Vikas Shivappa
2015-02-24 23:16 ` [PATCH 1/7] x86/intel_rdt: Intel Cache Allocation Technology detection Vikas Shivappa
2015-02-24 23:43 ` Borislav Petkov
2015-02-25 0:42 ` Vikas Shivappa
2015-02-25 11:21 ` Borislav Petkov
2015-02-26 18:19 ` Vikas Shivappa
2015-02-26 18:58 ` Borislav Petkov
2015-02-26 19:12 ` Vikas Shivappa
2015-02-26 19:22 ` Borislav Petkov
2015-03-03 23:34 ` Vikas Shivappa
2015-02-24 23:16 ` [PATCH 2/7] x86/intel_rdt: Adds support for Class of service management Vikas Shivappa
2015-02-24 23:16 ` [PATCH 3/7] x86/intel_rdt: Support cache bit mask for Intel CAT Vikas Shivappa
2015-02-27 12:12 ` Tejun Heo
2015-02-27 12:18 ` Tejun Heo
2015-02-27 19:34 ` Vikas Shivappa
2015-02-27 19:42 ` Tejun Heo
2015-02-27 21:38 ` Vikas Shivappa
2015-02-24 23:16 ` [PATCH 4/7] x86/intel_rdt: Implement scheduling support for Intel RDT Vikas Shivappa
2015-02-24 23:16 ` [PATCH 5/7] x86/intel_rdt: Software Cache for IA32_PQR_MSR Vikas Shivappa
2015-02-24 23:16 ` [PATCH 6/7] x86/intel_rdt: Intel haswell CAT enumeration Vikas Shivappa
2015-02-24 23:16 ` [PATCH 7/7] x86/intel_rdt: Add CAT documentation and usage guide Vikas Shivappa
2015-02-26 19:31 ` Hagen Paul Pfeifer
2015-02-25 9:26 ` [PATCH V4 0/7] x86/intel_rdt: Intel Cache Allocation Technology Peter Zijlstra
2015-02-25 16:40 ` Luck, Tony
2015-02-26 11:37 ` Ingo Molnar [this message]
2015-02-26 17:26 ` Vikas Shivappa
2015-02-26 18:16 ` Vikas Shivappa
2015-03-19 22:18 ` Vikas Shivappa
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=20150226113739.GB4191@gmail.com \
--to=mingo@kernel.org \
--cc=andi.kleen@intel.com \
--cc=dave.hansen@intel.com \
--cc=hpa@zytor.com \
--cc=kanaka.d.juvva@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=tony.luck@intel.com \
--cc=vikas.shivappa@intel.com \
--cc=vikas.shivappa@linux.intel.com \
--cc=will.auld@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.