From: He Chen <he.chen@linux.intel.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
xen-devel@lists.xen.org, Jan Beulich <jbeulich@suse.com>,
ChaoPeng <chao.p.peng@linux.intel.com>
Subject: Re: [RFC Design Doc] Intel L2 Cache Allocation Technology (L2 CAT) Feature enabling
Date: Fri, 13 May 2016 14:26:41 +0800 [thread overview]
Message-ID: <20160513062641.GA10649@HE> (raw)
In-Reply-To: <5734719002000078000EADCC@prv-mh.provo.novell.com>
On Thu, May 12, 2016 at 04:05:36AM -0600, Jan Beulich wrote:
> >>> On 12.05.16 at 11:40, <he.chen@linux.intel.com> wrote:
> > % Intel L2 Cache Allocation Technology (L2 CAT) Feature
> > % Revision 1.0
> >
> > \clearpage
> >
> > Hi all,
> >
> > We plan to bring new PQoS feature called Intel L2 Cache Allocation
> > Technology (L2 CAT) to Xen.
> >
> > L2 CAT is supported on Atom codename Goldmont and beyond. “Big-core”
> > Xeon does not support L2 CAT in current generations.
>
> Looks mostly like a direct (and hence reasonable) extension of what
> we have for L3 right now. One immediate question I have is whether
> tying this to per-socket information is a good idea. As soon as Xeon-s
> would also gain such functionality, things would (aiui) need to become
> per-core (as L2 is per core there iirc).
>
L2 Cache capability keeps the same through all cores in a socket, so we
make it per-socket to balance code complexity and accessibility.
I am not a expert in scheduler, do you mean in some cases, a domain
would apply different L2 cache access pattern when it is scheduled on
different cores even though the cores are in the same socket?
> The other question is whether with Xen we care enough about Atoms
> to add code that's of use only there.
>
L2 CAT is a platform independent feature although it firstly shows in
Atoms and I believe that it will appear in other platform soon.
Thanks,
-He
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-05-13 6:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-12 9:40 [RFC Design Doc] Intel L2 Cache Allocation Technology (L2 CAT) Feature enabling He Chen
2016-05-12 10:05 ` Jan Beulich
2016-05-13 6:26 ` He Chen [this message]
2016-05-13 6:48 ` Jan Beulich
2016-05-13 7:43 ` Andrew Cooper
2016-05-13 8:55 ` Jan Beulich
2016-05-13 9:23 ` Andrew Cooper
2016-05-13 16:17 ` Dario Faggioli
2016-05-16 8:23 ` He Chen
2016-05-16 9:44 ` Dario Faggioli
2016-05-12 10:06 ` Andrew Cooper
-- strict thread matches above, loose matches on Subject: below --
2016-05-12 9:31 He Chen
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=20160513062641.GA10649@HE \
--to=he.chen@linux.intel.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=chao.p.peng@linux.intel.com \
--cc=ian.jackson@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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 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.