From: Dario Faggioli <dario.faggioli@citrix.com>
To: He Chen <he.chen@linux.intel.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>,
Chao Peng <chao.p.peng@linux.intel.com>
Subject: Re: [RFC Design Doc] Intel L2 Cache Allocation Technology (L2 CAT) Feature enabling
Date: Mon, 16 May 2016 11:44:29 +0200 [thread overview]
Message-ID: <1463391869.18789.42.camel@citrix.com> (raw)
In-Reply-To: <20160516082357.GA17744@HE>
[-- Attachment #1.1: Type: text/plain, Size: 817 bytes --]
On Mon, 2016-05-16 at 16:23 +0800, He Chen wrote:
> As Andrew said, CLOS is currently managed per-domain in Xen and it
> works
> well so far. So in initial design, I am inclined to continue this
> behavior (per-socket) to L2 CAT to keep the consistency between L2
> and
> L3 CAT. Any thoughts?
>
FWIW, I think this is fine. If at some point we'll want something
different, we can always extend.
Perhaps, let's keep this (the fact that we may want to make things more
fine grained) in mind when designing the interface.
Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-05-16 9:44 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
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 [this message]
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=1463391869.18789.42.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=chao.p.peng@linux.intel.com \
--cc=he.chen@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.