From: Dario Faggioli <raistlin@linux.it>
To: George Dunlap <dunlapg@umich.edu>
Cc: andre.przywara@calxeda.com,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Matt Wilson <msw@amazon.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [Hackathon minutes] PV frontends/backends and NUMA machines
Date: Thu, 23 May 2013 19:21:21 +0200 [thread overview]
Message-ID: <1369329681.12423.252.camel@Solace> (raw)
In-Reply-To: <1369134657.12423.63.camel@Solace>
[-- Attachment #1.1: Type: text/plain, Size: 3333 bytes --]
On mar, 2013-05-21 at 13:10 +0200, Dario Faggioli wrote:
> Regarding #2 and #3, here they are the old patches (and other material)
> that I've been able to find so far on the subject.
>
> For HVM, the patches are originally from Andre (and I think they are the
> ones Matt is going to refresh and try to upstream):
> - July 2008: http://lists.xen.org/archives/html/xen-devel/2008-07/msg00582.html
> - February 2010: http://old-list-archives.xen.org/archives/html/xen-devel/2010-02/msg00279.html
>
> For PV, the patches are originally from Dulloor Rao, they come with a
> lot of policing and cover a lot o stuff that are upstream now, but there
> perhaps still are some useful bits:
> - April 2010: http://lists.xen.org/archives/html/xen-devel/2010-04/msg00103.html
> - August 2010: http://lists.xen.org/archives/html/xen-devel/2010-08/msg00008.html
>
Ok, sounds like I was misremembering. I've looked more thoroughly at the
various threads and at the patches that come with them and it turned out
that Dulloor's Aug 2010 series is about NUMA for HVM guests as well.
That is to say:
For HVM guest NUMA, here's what we have had:
- July 2008, from Andre: http://lists.xen.org/archives/html/xen-devel/2008-07/msg00582.html
- February 2010, from Andre: http://old-list-archives.xen.org/archives/html/xen-devel/2010-02/msg00279.html
- August 2010, from Dulloor: http://lists.xen.org/archives/html/xen-devel/2010-08/msg00008.html
For PV guest NUMA, here's what we have had:
- April 2010, from Dulloor: http://lists.xen.org/archives/html/xen-devel/2010-04/msg00103.html
- February 2010, from Dulloor: http://old-list-archives.xenproject.org/archives/html/xen-devel/2010-02/msg00630.html
- from Dulloor (implementing some kind of NUMA aware ballooning):
http://lists.xen.org/archives/html/xen-devel/2010-04/txtHhAq92jBSc.txt
Also, still for PV NUMA, this message (and of course the thread it comes
from) has some arguments about what are the advantages or disadvantages
of a couple of different interfaces, and I think it could be
interesting: http://lists.xen.org/archives/html/xen-devel/2010-04/msg00761.html
> The work on PV-NUMA appears to have been presented at a XenSummit,
> together by Dulloor and Jun from Intel, and there hence are slides and a
> video available:
> http://www.slideshare.net/xen_com_mgr/dulloor-xensummit#btnNext
> http://www.slideshare.net/xen_com_mgr/nakajima-numafinal
> http://vimeo.com/12295753
>
These, of course, are still valid.
So, whoever will get on to doing work on either PV or HVM NUMA, I think
it is well worthwhile to look at the threads and at the patches (the
Linux patches are there too). The code is not perfect and, as I already
said, there is a lot of overlap with stuff that are in right now, but
still, it probably is a better starting point than nothing! :-P
I'll "mirror" all this information on my NUMA roadmap Wiki page
(http://wiki.xen.org/wiki/Xen_NUMA_Roadmap), just to be even more sure
that we don't loose track of it.
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: 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-23 17:21 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
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 [this message]
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=1369329681.12423.252.camel@Solace \
--to=raistlin@linux.it \
--cc=andre.przywara@calxeda.com \
--cc=dunlapg@umich.edu \
--cc=msw@amazon.com \
--cc=stefano.stabellini@eu.citrix.com \
--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).