[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120322001722.GQ24602@redhat.com>
Date: Thu, 22 Mar 2012 01:17:22 +0100
From: Andrea Arcangeli <aarcange@...hat.com>
To: Dan Smith <danms@...ibm.com>
Cc: Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...e.hu>, Paul Turner <pjt@...gle.com>,
Suresh Siddha <suresh.b.siddha@...el.com>,
Mike Galbraith <efault@....de>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Lai Jiangshan <laijs@...fujitsu.com>,
Bharata B Rao <bharata.rao@...il.com>,
Lee Schermerhorn <Lee.Schermerhorn@...com>,
Rik van Riel <riel@...hat.com>,
Johannes Weiner <hannes@...xchg.org>,
linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [RFC] AutoNUMA alpha6
On Wed, Mar 21, 2012 at 11:52:42PM +0100, Andrea Arcangeli wrote:
> Your three numbers of mainline looked ok, it's still strange that
> numa01_same_node is identical to numa01_inverse_bind though. It
> shoudln't. same_node uses 1 numa node. inverse uses both nodes but
The only reasonable explanation I can imagine for the weird stuff
going on with "numa01_inverse" is that maybe it was compiled without
-DHARD_BIND? I forgot to specify -DINVERSE_BIND is a noop unless
-DHARD_BIND is specified too at the same time. -DINVERSE_BIND alone
results in the default build without -D parameters.
Now AutoNUMA has a bug and is real inverse bind too, I need to fix that.
In the meantime this is possible:
echo 0 >/sys/kernel/mm/autonuma/enabled
run numa01_inverse
echo 1 >/sys/kernel/mm/autonuma/enabled
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists