From: Dario Faggioli <raistlin@linux.it>
To: Jan Beulich <JBeulich@suse.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Tim Deegan <tim@xen.org>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [Hackathon minutes] PV frontends/backends and NUMA machines
Date: Tue, 21 May 2013 12:58:14 +0200 [thread overview]
Message-ID: <1369133894.12423.52.camel@Solace> (raw)
In-Reply-To: <519B6BFE02000078000D7A5A@nat28.tlf.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 1058 bytes --]
On mar, 2013-05-21 at 11:43 +0100, Jan Beulich wrote:
> >>> On 21.05.13 at 12:30, Dario Faggioli <raistlin@linux.it> wrote:
> > I remember such discussion (which, BTW, is here:
> > http://lists.xen.org/archives/html/xen-devel/2012-08/msg00332.html ).
> > However, wasn't that supposed to help only in case you want to confine
> > Dom0 on one specific node?
> >
> > That would definitely be already something, but not quite the same thing
> > that came up in Dublin, and that George was describing above (although I
> > agree it covers a sensible subset of it :-) ).
>
> I certainly meant to implement both such that multiple nodes would
> be permitted.
>
Well, sure, but then, again, how do you control which (and not only how
much) memory is taken from which node?
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: 198 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:[~2013-05-21 10:58 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-20 13:44 [Hackathon minutes] PV frontends/backends and NUMA machines Stefano Stabellini
2013-05-20 13:48 ` George Dunlap
2013-05-21 8:32 ` Tim Deegan
2013-05-21 8:47 ` George Dunlap
2013-05-21 8:49 ` George Dunlap
2013-05-21 10:03 ` Dario Faggioli
2013-05-21 9:20 ` Tim Deegan
2013-05-21 9:45 ` George Dunlap
2013-05-21 10:24 ` Tim Deegan
2013-05-21 10:28 ` George Dunlap
2013-05-21 11:12 ` Dario Faggioli
2013-05-21 9:53 ` Dario Faggioli
2013-05-21 10:06 ` Jan Beulich
2013-05-21 10:30 ` Dario Faggioli
2013-05-21 10:43 ` Jan Beulich
2013-05-21 10:58 ` Dario Faggioli [this message]
2013-05-21 11:47 ` Jan Beulich
2013-05-21 13:43 ` Dario Faggioli
2013-05-24 16:00 ` George Dunlap
2013-05-25 13:57 ` Dario Faggioli
2013-05-21 8:44 ` Roger Pau Monné
2013-05-21 9:24 ` Wei Liu
2013-05-21 9:53 ` George Dunlap
2013-05-21 10:17 ` Dario Faggioli
2013-05-21 11:10 ` Dario Faggioli
2013-05-23 17:21 ` Dario Faggioli
2013-05-22 1:28 ` Konrad Rzeszutek Wilk
2013-05-22 7:44 ` Dario Faggioli
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=1369133894.12423.52.camel@Solace \
--to=raistlin@linux.it \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xensource.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).