From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D8914C10DCE for ; Fri, 13 Mar 2020 17:34:14 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id AD98E206B1 for ; Fri, 13 Mar 2020 17:34:14 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726571AbgCMReN (ORCPT ); Fri, 13 Mar 2020 13:34:13 -0400 Received: from foss.arm.com ([217.140.110.172]:33714 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726442AbgCMReN (ORCPT ); Fri, 13 Mar 2020 13:34:13 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id B214431B; Fri, 13 Mar 2020 10:34:12 -0700 (PDT) Received: from e113632-lin (e113632-lin.cambridge.arm.com [10.1.194.46]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 794673F534; Fri, 13 Mar 2020 10:34:11 -0700 (PDT) References: <20200312165429.990-1-vincent.guittot@linaro.org> User-agent: mu4e 0.9.17; emacs 26.3 From: Valentin Schneider To: Vincent Guittot Cc: Ingo Molnar , Peter Zijlstra , Juri Lelli , Dietmar Eggemann , Steven Rostedt , Ben Segall , Mel Gorman , linux-kernel Subject: Re: [PATCH] sched/fair: improve spreading of utilization In-reply-to: Date: Fri, 13 Mar 2020 17:34:09 +0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Mar 13 2020, Vincent Guittot wrote: >> My point is that if we prevent this for migrate_util, it would make >> sense to prevent it for migrate_task, but it's not straightforward since > > hmm but we don't want to prevent this active balance for migrate_task > because of cases like the one you mentioned above. > > we might consider to finally select a CPU with only 1 running task > with migrate_util if there is no other CPU with more than 1 task. But > this would complexify the code and I don't think it's possible because > migrate_util is used to pull some utilizations from an overloaded > group which must have a CPU with a waiting task to be overloaded. > OK, so what we may want in the future is a tighter link between find_busiest_queue() and voluntary_active_balance(). I don't see a neat way of doing this right now, I'll ponder over it. Thanks for keeping up with my rambling.