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 S1754320AbdLTEWE convert rfc822-to-8bit (ORCPT <rfc822;w@1wt.eu>);
        Tue, 19 Dec 2017 23:22:04 -0500
Received: from mout.gmx.net ([212.227.17.20]:58621 "EHLO mout.gmx.net"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1754202AbdLTEWB (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Tue, 19 Dec 2017 23:22:01 -0500
Message-ID: <1513743697.6863.24.camel@gmx.de>
Subject: Re: [PATCH 3/4] sched: Comment on why sync wakeups try to run on
 the current CPU
From: Mike Galbraith <efault@gmx.de>
To: Peter Zijlstra <peterz@infradead.org>,
        Mel Gorman <mgorman@techsingularity.net>
Cc: Ingo Molnar <mingo@redhat.com>,
        Matt Fleming <matt@codeblueprint.co.uk>,
        LKML <linux-kernel@vger.kernel.org>
Date: Wed, 20 Dec 2017 05:21:37 +0100
In-Reply-To: <1513742961.6863.21.camel@gmx.de>
References: <20171218094327.19562-1-mgorman@techsingularity.net>
         <20171218094327.19562-4-mgorman@techsingularity.net>
         <20171219190644.3neuaenffj6tcxci@hirez.programming.kicks-ass.net>
         <1513742961.6863.21.camel@gmx.de>
Content-Type: text/plain; charset="ISO-8859-15"
X-Mailer: Evolution 3.20.5 
Mime-Version: 1.0
Content-Transfer-Encoding: 8BIT
X-Provags-ID: V03:K0:Losayw0rC1FOvyXyjF2hPifXP7lYVQ+Ytd9kDy1paVmiKp9d8Jl
 XxfmOXnYgMJZ5yYvx/A0vECLiECRAX6ekCT7ztatEIrY3ylXxPb72Pk8nU4z2hBoW+SR4x3
 5PLNbB6FDrrMvx6tZQ4jJaX2b9IAgDu3L0JP01beUWq/SBh2Pbl2eFQTbUpuic06caKMwja
 XeKmikuFcAmltSFDrSapQ==
X-UI-Out-Filterresults: notjunk:1;V01:K0:B5WuXogD104=:B//cF8q3iWnUWu/m7gFwsq
 PpvebcP4FYllonCkomV3QmXATuZ7xNDdA4yEla/GwNnT+o5kBWhIxe+8W0xdwc8RLsiXPvxFZ
 yo5FicXU6ipQY+rN8zXL4oXV75XHQPPEpNE0nigewJGMNuRZWN85mFJrgl2k7SjPxJYlJtEIG
 InjuCX24ZQe3lqqszQKOv8rzCA/Z/wBpzGmbvV6qErtTiOa0ArClTZm6dvZ7wbvoM1tCgwRfq
 KtXbX4vlfHgv7A9fmuDBg0PtSXO9VI2Rfq0pGozb39pBnbEABDfuDV73tITNd+UGYYTq2ouA0
 RO9rMXsa184GdBMjq84QH3C2kJYL6nWcVV9Q7WLRX//Ye8bjvoqkIApGxeCID969ckif7Nkw9
 EBnOEChIDlAvPWPOZtVrhYfNJRVD4z0NMn9JwxCjOqATjm04WeMadJqpSt9sAqzQRlEEtgpyo
 LRWL374F+kN1U2VCjw95QWs46WzP9CLHAzbjmkoZLSK/WBI8MdhCwbYq+jBdCSkCt8lbgUxyR
 fNGJ0Tu2Ob9gqUO3LQn3wix3SYpJHHeiyzcThAivUaxTr6FHRS+2kIADOdn7rpOnJtWaZEicW
 4oGO4NrtALOo8vR+Yn/EpqJqCuS+7DR8n/59DQq08IbcKvfcE5IVSBkr76JNqHaqRisKQw/E0
 t7fk9azFTntGVVSaVJ6WsOqXA6zQczMWGjQRUFhuhaRKwNKwJZD5zheSU6mAPnXfa0i+BYCxs
 sbnUG7BShCO698g+rkkh03tlc9T+1LV3+PDom19x8XeSuY2giVE/P25Dkm37MP7WpdJf9ikuw
 bVOPHE7niTrVKjrE5QCwqQJhMGjb2DFf8eIqAVohgMwbkr7M+g=
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Wed, 2017-12-20 at 05:09 +0100, Mike Galbraith wrote:
>  Nope, stacking based upon that
> hint is most definitely not a good idea :)

Except when heavily loaded.  The only thing worse for communicating
hogs being stacked is communicating hogs talking with another hog
between them.

	-Mike