From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1753091AbdDMXiK (ORCPT <rfc822;w@1wt.eu>);
        Thu, 13 Apr 2017 19:38:10 -0400
Received: from mx1.redhat.com ([209.132.183.28]:48084 "EHLO mx1.redhat.com"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1752365AbdDMXiH (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Thu, 13 Apr 2017 19:38:07 -0400
DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 255693B708
Authentication-Results: ext-mx06.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
Authentication-Results: ext-mx06.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=riel@redhat.com
DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 255693B708
Message-ID: <1492126685.8850.189.camel@redhat.com>
Subject: Re: [RFC 2/3] sched/topology: fix sched groups on NUMA machines
 with mesh topology
From: Rik van Riel <riel@redhat.com>
To: lvenanci@redhat.com, Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, lwang@redhat.com,
        Mike Galbraith <efault@gmx.de>, Thomas Gleixner <tglx@linutronix.de>,
        Ingo Molnar <mingo@kernel.org>
Date: Thu, 13 Apr 2017 19:38:05 -0400
In-Reply-To: <dea71fe0-9e39-43c8-2710-13767b14ce63@redhat.com>
References: <1492091769-19879-1-git-send-email-lvenanci@redhat.com>
         <1492091769-19879-3-git-send-email-lvenanci@redhat.com>
         <20170413154812.vrtkdyzgkrywj2no@hirez.programming.kicks-ass.net>
         <5166d6ba-c8e6-c60e-61af-d32124234bb9@redhat.com>
         <dea71fe0-9e39-43c8-2710-13767b14ce63@redhat.com>
Organization: Red Hat, Inc
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.30]); Thu, 13 Apr 2017 23:38:07 +0000 (UTC)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Thu, 2017-04-13 at 18:06 -0300, Lauro Venancio wrote:

> Just for clarification, I am sending the nodes distance table for the
> two most common typologies affected by this issue.

What do the sched groups look like for these topologies,
before and after your patch series?

> 4 nodes, ring topology
> node distances:
> node   0   1   2   3
>   0:  10  20  30  20
>   1:  20  10  20  30
>   2:  30  20  10  20
>   3:  20  30  20  10
> 
> 8 node, mesh topology
> node distances:
> node   0   1   2   3   4   5   6   7
>   0:  10  16  16  22  16  22  16  22
>   1:  16  10  16  22  22  16  22  16
>   2:  16  16  10  16  16  16  16  22
>   3:  22  22  16  10  16  16  22  16
>   4:  16  22  16  16  10  16  16  16
>   5:  22  16  16  16  16  10  22  22
>   6:  16  22  16  22  16  22  10  16
>   7:  22  16  22  16  16  22  16  10