From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932201AbdKGT4n (ORCPT ); Tue, 7 Nov 2017 14:56:43 -0500 Received: from mail.skyhub.de ([5.9.137.197]:60134 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754744AbdKGT4m (ORCPT ); Tue, 7 Nov 2017 14:56:42 -0500 Date: Tue, 7 Nov 2017 20:56:24 +0100 From: Borislav Petkov To: Dave Hansen Cc: Peter Zijlstra , linux-kernel@vger.kernel.org, tony.luck@intel.com, tim.c.chen@linux.intel.com, hpa@linux.intel.com, rientjes@google.com, imammedo@redhat.com, prarit@redhat.com, toshi.kani@hp.com, brice.goglin@gmail.com, mingo@kernel.org Subject: Re: [RFC][PATCH] x86, sched: allow topolgies where NUMA nodes share an LLC Message-ID: <20171107195624.dd4rlqnjnitqkvai@pd.tnic> References: <20171106221500.310295D7@viggo.jf.intel.com> <20171107083019.GG3326@worktop> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170609 (1.8.3) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Nov 07, 2017 at 08:22:19AM -0800, Dave Hansen wrote: > FWIW, I don't consider the current situation broken. Nobody ever > promised the kernel that a NUMA node would never happen inside a socket, > or inside a cache boundary enumerated in CPUID. Right, I don't think the name matters. A synthetic flag which you set in .../cpu/intel.c for each SNC configuration and then check said flag in topology setup code is cleaner than having to add all those vendor/model checks ... -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.