Received: by 2002:a05:6a10:6d10:0:0:0:0 with SMTP id gq16csp175580pxb; Mon, 11 Apr 2022 22:16:19 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwzMR1iwnWS68qIUaOQDqV2t4BKWFmP1esbXKvezXRGTbQ1VIkgcyTZwfu3vk8IT655iUv0 X-Received: by 2002:aa7:920b:0:b0:505:66a5:3029 with SMTP id 11-20020aa7920b000000b0050566a53029mr2831757pfo.40.1649740579205; Mon, 11 Apr 2022 22:16:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1649740579; cv=none; d=google.com; s=arc-20160816; b=LHJUiNq3+LWsyv+hLluyFkKt4fCXTWzF96WuiFmBAH/CU2ym9pAhrldjZFByMkAkrS Rxgol4rVVsFh2pn3pHgxM+eoKriKw8hoW6aQRFiaYwUxI4s5Daq7fX9+9f3Kk9n/Ac/g YjDwjWe/I+vg8Tul2qr9frLEu4NFlVjA+GGYNch9Q1EGRsl/avzuXBMQH8es7EI3pIbv VUxP4/VtpqYd46j54bpaiWHqWC/Z1gWc/cHwqDbdfHcnt87pZDxlhJyZQmG1IkyL4IEv q7bs3DHK3Rx4YwRk+xK7GjR5YbJQaFCjdYegD+VEfcovGdA6SOdmjzB8v2DbCMLu+Mwn jhyg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date; bh=SLaXR5K5sFYy7EN27C3xbKKuQLDbwGkkdG7RKrB7iew=; b=06u8p1dEuzgNTeG98ZwDJTRYIjyPDiDbDZMpic0p7R9zfsAH4F6qUOqvwD+orupcwJ YMLdbN4+74yBSrvnI97ORetM0hDxThkTKz1udkcJQN2aKozw1ngBmn72SPdjKcWFJzvN kl7rT7yASeSzqJ8Wgkwafy5J1mY5EcUSgLmD0wvNRmTtQk22pVNyoqWd4zimHzhcEUp0 U1w2e/2CsO1I1VCA7YegvZ6G7dAQpFM2ElsFzDjHiOnbLE09p5csy2ZGrLDkWlhfODXM IHfTKOm8S2vR7at4rS4dBn3fmFqOZeEoMDcjaRrZLls/xBxlOrM6DNdpelY4S8YzBsXC z6Aw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id k4-20020a056a00134400b004faa59148b8si11250886pfu.211.2022.04.11.22.16.06; Mon, 11 Apr 2022 22:16:19 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242851AbiDIRar (ORCPT + 99 others); Sat, 9 Apr 2022 13:30:47 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42664 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231684AbiDIRan (ORCPT ); Sat, 9 Apr 2022 13:30:43 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0651E83036 for ; Sat, 9 Apr 2022 10:28:34 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 00A7C60DE3 for ; Sat, 9 Apr 2022 17:28:33 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id B653CC385A4; Sat, 9 Apr 2022 17:28:30 +0000 (UTC) Date: Sat, 9 Apr 2022 13:28:29 -0400 From: Steven Rostedt To: Qais Yousef Cc: Vincent Guittot , Dietmar Eggemann , mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com, bsegall@google.com, mgorman@suse.de, linux-kernel@vger.kernel.org, parth@linux.ibm.com, chris.hyser@oracle.com, pkondeti@codeaurora.org, Valentin.Schneider@arm.com, patrick.bellasi@matbug.net, David.Laight@aculab.com, pjt@google.com, pavel@ucw.cz, tj@kernel.org, qperret@google.com, tim.c.chen@linux.intel.com, Wei Wang Subject: Re: [PATCH 0/6] Add latency_nice priority Message-ID: <20220409132829.16b03d69@rorschach.local.home> In-Reply-To: <20220409170841.upcimeak2ch3aj35@wubuntu> References: <20220311161406.23497-1-vincent.guittot@linaro.org> <7a7e1e21-df3d-4623-d9cd-51f5272919d5@arm.com> <20220401121525.flngciwjtkn3mwlv@airbuntu> <20220409170841.upcimeak2ch3aj35@wubuntu> X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.33; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-6.7 required=5.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,RCVD_IN_DNSWL_HI,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 9 Apr 2022 18:08:41 +0100 Qais Yousef wrote: > One other corner case to consider if you're working on next version is what > should happen when there are multiple tasks of the same priority on the rq. RT > scheduler will push/pull tasks to ensure the task will get to run ASAP if > there's another cpu at lower priority is available. Seems a lot of complexity > to add to CFS, but at the same time if 2 important tasks require low latency > are on the same rq, one of them will suffer without introducing the ability to > migrate one of them where it can get to run sooner. Instead of having the greedy algorithm of the RT push/pull logic, how hard would it be to have the load balancer know of these tasks, and try to keep them on different CPUs? When two are queued on the same CPU, could it be possible to just trigger load balancing and let it do the work? -- Steve