From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754653Ab2FFHLY (ORCPT ); Wed, 6 Jun 2012 03:11:24 -0400 Received: from mail-wi0-f178.google.com ([209.85.212.178]:40612 "EHLO mail-wi0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751330Ab2FFHLX (ORCPT ); Wed, 6 Jun 2012 03:11:23 -0400 Date: Wed, 6 Jun 2012 09:11:17 +0200 From: Ingo Molnar To: David Rientjes Cc: a.p.zijlstra@chello.nl, hpa@zytor.com, linux-kernel@vger.kernel.org, yinghai@kernel.org, tj@kernel.org, tglx@linutronix.de, linux-tip-commits@vger.kernel.org Subject: Re: [tip:sched/core] x86/numa: Allow specifying node_distance() for numa=fake Message-ID: <20120606071117.GE17808@gmail.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * David Rientjes wrote: > On Wed, 9 May 2012, tip-bot for Peter Zijlstra wrote: > > > Commit-ID: 94c0dd3278dd3eae52eabf0fb77d472d0dd3e373 > > Gitweb: http://git.kernel.org/tip/94c0dd3278dd3eae52eabf0fb77d472d0dd3e373 > > Author: Peter Zijlstra > > AuthorDate: Wed, 18 Apr 2012 19:04:17 +0200 > > Committer: Ingo Molnar > > CommitDate: Wed, 9 May 2012 13:28:59 +0200 > > > > x86/numa: Allow specifying node_distance() for numa=fake > > > > Allows emulating more interesting NUMA configurations like a quad > > socket AMD Magny-Cour: > > > > "numa=fake=8:10,16,16,22,16,22,16,22, > > 16,10,22,16,22,16,22,16, > > 16,22,10,16,16,22,16,22, > > 22,16,16,10,22,16,22,16, > > 16,22,16,22,10,16,16,22, > > 22,16,22,16,16,10,22,16, > > 16,22,16,22,16,22,10,16, > > 22,16,22,16,22,16,16,10" > > > > Which has a non-fully-connected topology. > > > > I like this support and I'm pretty sure you used it to > reproduce my problems with sched/numa locally, but I think it > would be better to seperate it out as a different parameter > such as slit=fake so that we can still use it to fake the SLIT > of our NUMA machines without requiring numa=fake which > provides no guarantees to break the nodes along physical > boundaries. > > So without seperating it out into slit=fake, we can't change > this information without changing the SLIT itself and that > makes debugging harder. Makes sense - wanna send a patch? Thanks, Ingo