linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Elena Ufimtseva <ufimtseva@gmail.com>
Cc: <xen-devel@lists.xenproject.org>, <akpm@linux-foundation.org>,
	<wency@cn.fujitsu.com>, <x86@kernel.org>,
	<linux-kernel@vger.kernel.org>, <tangchen@cn.fujitsu.com>,
	<mingo@redhat.com>, <david.vrabel@citrix.com>, <hpa@zytor.com>,
	<boris.ostrovsky@oracle.com>, <tglx@linutronix.de>,
	<stefano.stabellini@eu.citrix.com>, <ian.campbell@citrix.com>
Subject: Re: [Xen-devel] [PATCH RESEND v2 0/2] xen: vnuma introduction for pv guest
Date: Tue, 19 Nov 2013 08:18:35 +0100	[thread overview]
Message-ID: <1384845515.19880.13.camel@Abyss> (raw)
In-Reply-To: <1384811922-14642-1-git-send-email-ufimtseva@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1025 bytes --]

On lun, 2013-11-18 at 16:58 -0500, Elena Ufimtseva wrote:
> Xen vnuma introduction.
> 
> The patchset introduces vnuma to paravirtualized Xen guests
> runnning as domU.
> Xen subop hypercall is used to retreive vnuma topology information.
> Bases on the retreived topology from Xen, NUMA number of nodes,
> memory ranges, distance table and cpumask is being set.
> If initialization is incorrect, sets 'dummy' node and unsets
> nodemask. vNUMA topology is constructed by Xen toolstack.
> 
> Example of vnuma enabled pv domain dmesg:
> 
Mmm... So, why the resend? When you do things like this, you usually
tell the reason, if only, to let people know what happened and which
series they should actually look at and review. :-)

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 #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

      parent reply	other threads:[~2013-11-19  7:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-18 21:58 [PATCH RESEND v2 0/2] xen: vnuma introduction for pv guest Elena Ufimtseva
2013-11-18 21:58 ` [PATCH RESEND v2 1/2] xen: vnuma support for PV guests running as domU Elena Ufimtseva
2013-11-19 11:53   ` David Vrabel
2013-11-18 21:58 ` [PATCH RESEND v2 2/2] xen: enable vnuma for PV guest Elena Ufimtseva
2013-11-19 11:54   ` David Vrabel
2013-11-19 14:16     ` Konrad Rzeszutek Wilk
2013-11-19 14:35       ` David Vrabel
2013-11-19 14:46         ` Konrad Rzeszutek Wilk
2013-11-19 14:56           ` David Vrabel
2013-11-19 15:19             ` Konrad Rzeszutek Wilk
2013-11-19 15:55               ` David Vrabel
2013-11-19 16:20                 ` Konrad Rzeszutek Wilk
2013-11-23 16:48             ` [Xen-devel] " Dario Faggioli
2013-11-19  7:18 ` 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=1384845515.19880.13.camel@Abyss \
    --to=dario.faggioli@citrix.com \
    --cc=akpm@linux-foundation.org \
    --cc=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=hpa@zytor.com \
    --cc=ian.campbell@citrix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=tangchen@cn.fujitsu.com \
    --cc=tglx@linutronix.de \
    --cc=ufimtseva@gmail.com \
    --cc=wency@cn.fujitsu.com \
    --cc=x86@kernel.org \
    --cc=xen-devel@lists.xenproject.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 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).