From: Dario Faggioli <raistlin@linux.it>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: Andre Przywara <andre.przywara@amd.com>,
Anil Madhavapeddy <anil@recoil.org>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Andrew Cooper <Andrew.Cooper3@citrix.com>,
Konrad Wilk <konrad.wilk@oracle.com>,
xen-devel <xen-devel@lists.xen.org>,
Jan Beulich <JBeulich@suse.com>,
Kurt Hackel <kurt.hackel@oracle.com>,
"Zhang, Yang Z" <yang.z.zhang@intel.com>
Subject: Re: NUMA TODO-list for xen-devel
Date: Wed, 08 Aug 2012 01:49:54 +0200 [thread overview]
Message-ID: <1344383394.1890.11.camel@Solace> (raw)
In-Reply-To: <ed108492-5601-4bc3-8a5f-a8a7cb5916fb@default>
[-- Attachment #1.1: Type: text/plain, Size: 2675 bytes --]
On Fri, 2012-08-03 at 15:22 -0700, Dan Magenheimer wrote:
> Hi Dario --
>
Hello Dan,
> Thanks for your great work on NUMA... an interest area of
> mine but one, sadly, I haven't been able to give much time to,
> so I'm glad you've taken this bull by the horns.
>
Trying to... Let's see! :-P
> I've been sitting on an idea for some time that probably
> deserves some exposure on your list. Naturally, it involves
> my favorite topic tmem (readers, please don't tune out yet :-).
>
It sure does! I've already put something quite generic about "memory
sharing" there, because I know that it has all but trivial interactions
with the improved NUMA support I am/we are trying to envision.
The fact that it is, as I said, generic, is due to my ignorance (let's
say for now) of the whole tmem thing, so thanks for the contribution,
it's very useful to hear your point of view on this!
> It has occurred to me that a fundamental tenet of NUMA
> is to put infrequently used data on "other" nodes, while
> pulling frequently used data onto a "local" node.
>
> Tmem very nicely separates infrequently-used data from
> frequently-used data with an API/ABI that is now fully
> implemented in upstream Linux.
>
I see, and it seems nice.
> [..]
>
> Naturally, this doesn't solve any NUMA problems at all for
> tmem-ignorant or tmem-disabled guests, but if it works
> sufficiently well for tmem-enabled guests, that might
> encourage other OS's to do a simple implementation of tmem.
>
Sure. In my opinion, this is not an area where we could aim at "solving
every problem for everyone". However, we should definitely target having
a sensible solution for default and/or most common use cases and
scenarios.
> Sadly, I'm not able to invest much time in this idea,
> but the combination of tmem and NUMA might interest some
> developers and/or grad students, in which case I'd be happy
> to spend a little time assisting.
>
That's definitely the case. I've tried to put a summary of what you said
in this mail to the Wiki (http://wiki.xen.org/wiki/Xen_NUMA_Roadmap) and
also put your contact next to it. Feel free to update/correct if you fin
something wrong. :-P
> I'll be at Xen Summit for at least the first day, so we
> can chat more if you are interested.
>
I indeed am interested, so let's make that happen! :-)
Thanks and Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://retis.sssup.it/people/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
prev parent reply other threads:[~2012-08-07 23:49 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-01 16:16 NUMA TODO-list for xen-devel Dario Faggioli
2012-08-01 16:24 ` Dario Faggioli
2012-08-01 16:30 ` Andrew Cooper
2012-08-01 16:47 ` Dario Faggioli
2012-08-01 16:53 ` Andrew Cooper
2012-08-02 9:40 ` Jan Beulich
2012-08-02 13:21 ` Dario Faggioli
2012-08-01 16:32 ` Anil Madhavapeddy
2012-08-01 16:58 ` Dario Faggioli
2012-08-02 0:04 ` Malte Schwarzkopf
2012-08-07 23:53 ` Dario Faggioli
2012-08-02 1:04 ` Zhang, Yang Z
2012-08-07 22:56 ` Dario Faggioli
2012-08-02 9:43 ` Jan Beulich
2012-08-02 13:34 ` Dario Faggioli
2012-08-02 14:07 ` Jan Beulich
2012-08-02 16:36 ` George Dunlap
2012-08-03 9:23 ` Jan Beulich
2012-08-03 9:48 ` Andre Przywara
2012-08-03 10:03 ` Jan Beulich
2012-08-03 22:40 ` Dan Magenheimer
2012-08-03 11:00 ` George Dunlap
2012-08-03 22:34 ` Dan Magenheimer
2012-08-06 7:15 ` Jan Beulich
2012-08-06 16:28 ` Dan Magenheimer
2012-08-03 10:02 ` Andre Przywara
2012-08-03 10:40 ` Jan Beulich
2012-08-03 11:26 ` Andre Przywara
2012-08-03 11:38 ` Jan Beulich
2012-08-03 13:14 ` Dario Faggioli
2012-08-03 13:52 ` Jan Beulich
2012-08-03 22:42 ` Dan Magenheimer
2012-08-08 7:07 ` Dario Faggioli
2012-08-08 7:43 ` Dario Faggioli
2012-08-03 22:22 ` Dan Magenheimer
2012-08-07 23:49 ` Dario Faggioli [this message]
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=1344383394.1890.11.camel@Solace \
--to=raistlin@linux.it \
--cc=Andrew.Cooper3@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andre.przywara@amd.com \
--cc=anil@recoil.org \
--cc=dan.magenheimer@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=kurt.hackel@oracle.com \
--cc=xen-devel@lists.xen.org \
--cc=yang.z.zhang@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 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).