mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mel Gorman <mgorman@suse.de>
To: Dario Faggioli <dario.faggioli@citrix.com>
Cc: "torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	David Vrabel <david.vrabel@citrix.com>,
	"Xen-devel@lists.xen.org" <Xen-devel@lists.xen.org>,
	Wei Liu <wei.liu2@citrix.com>
Subject: Re: [Xen-devel] NUMA_BALANCING and Xen PV guest regression in 3.20-rc0
Date: Mon, 23 Feb 2015 15:46:37 +0000	[thread overview]
Message-ID: <20150223154637.GX3087@suse.de> (raw)
In-Reply-To: <1424704425.5819.38.camel@citrix.com>

On Mon, Feb 23, 2015 at 03:13:48PM +0000, Dario Faggioli wrote:
> Hi everyone,
> 
> On Thu, 2015-02-19 at 17:01 +0000, Mel Gorman wrote:
> > On Thu, Feb 19, 2015 at 01:06:53PM +0000, David Vrabel wrote:
> 
> > I cannot think of a reason why this would fail for NUMA balancing on bare
> > metal. The PAGE_NONE protection clears the present bit on p[te|md]_modify
> > so the expectations are matched before or after the patch is applied. So,
> > for bare metal at least
> > 
> > Acked-by: Mel Gorman <mgorman@suse.de>
> > 
> > I *think* this will work ok with Xen but I cannot 100% convince myself.
> > I'm adding Wei Liu to the cc who may have a Xen PV setup handy that
> > supports NUMA and may be able to test the patch to confirm.
> > 
> I'm not Wei, but I've been able to test a kernel with David's patch in
> the following conditions:
> 

Thanks very much, it's appreciated.

>  1. as Dom0 kernel, when Xen does not have any virtual NUMA support
>  2. as DomU PV kernel, when Xen does not have any virtual NUMA support
>  3. as DomU PV kernel, when Xen _does_ _have_ virtual NUMA support
>     (i.e., Wei's code)
> 
> Cases 1. and 2. have been, I believe, tested by David already, but
> anyways... :-)
> 
> Case 3. worked well for me, as the following commands show. In fact,
> with this in guest config file:
> 
> <SNIP>
>
> And this:
> 
>     root@test-pv:~# grep numa /proc/vmstat 
>     numa_hit 65987
>     numa_miss 0
>     numa_foreign 0
>     numa_interleave 14473
>     numa_local 58642
>     numa_other 7345
>     numa_pte_updates 596
>     numa_huge_pte_updates 0
>     numa_hint_faults 479
>     numa_hint_faults_local 420
>     numa_pages_migrated 51
> 
> So, yes, I would say this wok with Xen, is that correct, Mel?
> 

Yes, these stats indicate that NUMA balancing is active. There is no
much activity but it's there.

> I'll give it a try at running more complex stuff like 'perf bench numa'
> inside the guest and see what happens...
> 

Thanks.

-- 
Mel Gorman
SUSE Labs

  reply	other threads:[~2015-02-23 15:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-19 13:06 David Vrabel
2015-02-19 17:01 ` Mel Gorman
2015-02-23 15:13   ` [Xen-devel] " Dario Faggioli
2015-02-23 15:46     ` Mel Gorman [this message]
2015-02-19 23:09 ` Linus Torvalds
2015-02-20 10:28   ` [Xen-devel] " David Vrabel
2015-02-20  1:05 ` Kirill A. Shutemov
2015-02-20  1:49   ` Linus Torvalds
2015-02-20 10:47     ` [Xen-devel] " Andrew Cooper
2015-02-20 11:29       ` Kirill A. Shutemov
2015-02-20 11:54         ` Andrew Cooper

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=20150223154637.GX3087@suse.de \
    --to=mgorman@suse.de \
    --cc=Xen-devel@lists.xen.org \
    --cc=dario.faggioli@citrix.com \
    --cc=david.vrabel@citrix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=wei.liu2@citrix.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

Powered by JetHome