Received: by 2002:a25:e7d8:0:0:0:0:0 with SMTP id e207csp1970734ybh; Fri, 13 Mar 2020 10:34:43 -0700 (PDT) X-Google-Smtp-Source: ADFU+vvcVeaZqollBXF48WkfvlXvBPwysiFQF8uHF75wT3PLDG0P8Vm1uBX8QJ59LNqCg8orN4K0 X-Received: by 2002:a9d:336:: with SMTP id 51mr11976506otv.202.1584120883061; Fri, 13 Mar 2020 10:34:43 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1584120883; cv=none; d=google.com; s=arc-20160816; b=iB1tcqImsZxn+RAvDd9LztAhbDYNs7F3oaYPSuqaDz6qpObUGVYv6m3lqS5ptFw+If UbyDAEjxlcYnFzIKwqP/is1NgipUgbNJfEsgfNG8Ea2VxCcKeBSA63AvUfxkiVJC05cP SaT22Ncby8X+Y6WkZUlEUm1W5kne0hy7Q0c9K28oUaV50qWj+mlyuUabrYuJ2rKG49jo OVRqLgGF1AV/Hs9twfAFtF8j+8gtOG6XqnX18WcBt7GggPuED64PHrXkhWPzsDDisOX/ YdwNXw6PGl7nJ+j9fkv1hvxJmELW3uv0ad2qA0KhnYZeq8B8RseO3hB+vBHccbKqn3IP NMfQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:date:in-reply-to :subject:cc:to:from:user-agent:references; bh=WJ97PpGWV2yH/EtwAcXTJdo2OWIPthH6FxMsuBKn0+M=; b=jZvPFcKjXZzvaBL/KXARR/h3wyq/YKI0Wo7qFMDvyGhNvLZmQWZpF/TcdQjhCvr6bW yZzbf0kD8IT1ReTdn6Jb52ZVVCMWzmnpyPmdWrfXmKzsSZwUTFlqh/c1OJ7dXu0XJS4P A3Dx44uxlJ2ruI4czJUk1yq8X0eAIeAQZZMI/+iQkvHyERQQ2kA6iqfxA3UQOxFkCMam 3GvFG7wmBsIuK9cxM+6+IkfoeZP+76QBKNbq1XWO4r8DJiGKdbj5ECnyQ3EXMH34sDXO TGpUjUIoOM8Lq9QaJYDDqBBp+RdYHz7ppOZfL1uRd6xinJY67aJgtyg5hwsROW5hg/pr l4WA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id z23si2157690oih.275.2020.03.13.10.34.28; Fri, 13 Mar 2020 10:34:43 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726543AbgCMReN (ORCPT + 99 others); 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.