[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3908561D78D1C84285E8C5FCA982C28F1E06EDDD@ORSMSX108.amr.corp.intel.com>
Date: Wed, 27 Feb 2013 17:50:49 +0000
From: "Luck, Tony" <tony.luck@...el.com>
To: Yinghai Lu <yinghai@...nel.org>
CC: Yasuaki Ishimatsu <isimatu.yasuaki@...fujitsu.com>,
Don Morris <don.morris@...com>,
"H. Peter Anvin" <hpa@...or.com>, Tejun Heo <tj@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Thomas Renninger <trenn@...e.de>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Tim Gardner <tim.gardner@...onical.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"mingo@...hat.com" <mingo@...hat.com>,
"x86@...nel.org" <x86@...nel.org>,
"a.p.zijlstra@...llo.nl" <a.p.zijlstra@...llo.nl>,
"Sakkinen, Jarkko" <jarkko.sakkinen@...el.com>,
"tangchen@...fujitsu.com" <tangchen@...fujitsu.com>
Subject: RE: sched: CPU #1's llc-sibling CPU #0 is not on the same node!
> b. it will be freed to slub before run time.
> like init code and initrd disk.
If this is a problem - I'd be inclined to disable the code that frees it. It's only
a few hundred KB of code, and possibly a few MB of initrd. Too small to
worry about on a hot pluggable server.
> In that case, so they should just boot system with numa=off.
But we will still care about NUMA locality.
-Tony
--
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