Received: by 2002:ac0:a594:0:0:0:0:0 with SMTP id m20-v6csp1454100imm; Tue, 22 May 2018 04:29:12 -0700 (PDT) X-Google-Smtp-Source: AB8JxZplAhdm246XuhbLGVXY7b8qHbPsESZKTDsoYvcPsgD2txjqXZDlYHbwaj94xtyXvMGYfZMJ X-Received: by 2002:a17:902:b946:: with SMTP id h6-v6mr25044916pls.3.1526988552272; Tue, 22 May 2018 04:29:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1526988552; cv=none; d=google.com; s=arc-20160816; b=x51UhFHFx6bJrYq5kJ4YSBczfvURsl8hYIMiira32cYoTwOyoduHyMN74IFOgMNKzk bFhVt+hgo6g8PjrG9TvtWxskR/ycbGGs4J7imVn74fZeDL3VhVUC0GrnRfVlLYFwRFuL d5C0fcJ5bBRmgMjReAD3ZxphvweDu31aySofQLz6/gCV+hX66GES9D8y4KPq4Ffw/TBf ojPYF2FusP1NGYMxmF+e/r+3lZEZn5YGSUBPpaHLE9q3a7LefHBDowALdv15LcnoVVhb 8koMa3HDfzlBuj7dwXjTeieL+Xn1+C5MwCwMZ6Wehbw9qKF91hXt3KqEom2f3CLrYjj3 IrVg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :arc-authentication-results; bh=J0zgz/9fYYSzEQbITZO+diNO12TQDjpnQAr6i1w3DU0=; b=Id3mtQBnL6R0UC+Qvmhqk7zqk9aCXuH1YUZk3I2TJB2+BByFAaKROZSGmJYggScjRM LQ8iS9NsYBOy8OUNO5S+Eru9aW0wMO5saZFeVEUYIC0CnNRMHQ+iEBm8HyWOqDSAObic qEMWEGmc3Lzm2BQYd2vOEnnC9DZG4LKxASUzn72AYn/w7IYnpEM5JexxJSMweo2CxMtY dnzTmXdy7f5wjDmv3ACWq81HrJrp7UwrNSueJDijoieLy5ZvBb3A/1obACMNK1Wvfeh+ AI3vhFzQQolY+WNUHIhsJ95DTwVSN9V1ivDh7eREG/lTYRWY7L46ohLstxRyx0OAJqSL BOwA== 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 g9-v6si15912216plt.232.2018.05.22.04.28.57; Tue, 22 May 2018 04:29:12 -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 S1751368AbeEVL1h (ORCPT + 99 others); Tue, 22 May 2018 07:27:37 -0400 Received: from cloudserver094114.home.pl ([79.96.170.134]:53878 "EHLO cloudserver094114.home.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751060AbeEVL1e (ORCPT ); Tue, 22 May 2018 07:27:34 -0400 Received: from 79.184.253.39.ipv4.supernova.orange.pl (79.184.253.39) (HELO aspire.rjw.lan) by serwer1319399.home.pl (79.96.170.134) with SMTP (IdeaSmtpServer 0.83) id ce5b0ac80e0f4b2e; Tue, 22 May 2018 13:27:33 +0200 From: "Rafael J. Wysocki" To: "Rafael J. Wysocki" Cc: Joel Fernandes , Viresh Kumar , "Joel Fernandes (Google.)" , Linux Kernel Mailing List , "Rafael J . Wysocki" , Peter Zijlstra , Ingo Molnar , Patrick Bellasi , Juri Lelli , Luca Abeni , Todd Kjos , Claudio Scordino , kernel-team@android.com, Linux PM Subject: Re: [PATCH v2] schedutil: Allow cpufreq requests to be made even when kthread kicked Date: Tue, 22 May 2018 13:26:55 +0200 Message-ID: <1572088.N2D3R5Hx9f@aspire.rjw.lan> In-Reply-To: References: <20180518185501.173552-1-joel@joelfernandes.org> <20180521161346.GB14065@joelaf.mtv.corp.google.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tuesday, May 22, 2018 12:02:24 PM CEST Rafael J. Wysocki wrote: > On Mon, May 21, 2018 at 6:13 PM, Joel Fernandes wrote: > > On Mon, May 21, 2018 at 10:29:52AM +0200, Rafael J. Wysocki wrote: > >> On Mon, May 21, 2018 at 7:14 AM, Viresh Kumar wrote: > >> > On 18-05-18, 11:55, Joel Fernandes (Google.) wrote: > >> >> From: "Joel Fernandes (Google)" > >> >> > >> >> Currently there is a chance of a schedutil cpufreq update request to be > >> >> dropped if there is a pending update request. This pending request can > >> >> be delayed if there is a scheduling delay of the irq_work and the wake > >> >> up of the schedutil governor kthread. > >> >> > >> >> A very bad scenario is when a schedutil request was already just made, > >> >> such as to reduce the CPU frequency, then a newer request to increase > >> >> CPU frequency (even sched deadline urgent frequency increase requests) > >> >> can be dropped, even though the rate limits suggest that its Ok to > >> >> process a request. This is because of the way the work_in_progress flag > >> >> is used. > >> >> > >> >> This patch improves the situation by allowing new requests to happen > >> >> even though the old one is still being processed. Note that in this > >> >> approach, if an irq_work was already issued, we just update next_freq > >> >> and don't bother to queue another request so there's no extra work being > >> >> done to make this happen. > >> > > >> > Now that this isn't an RFC anymore, you shouldn't have added below > >> > paragraph here. It could go to the comments section though. > >> > > >> >> I had brought up this issue at the OSPM conference and Claudio had a > >> >> discussion RFC with an alternate approach [1]. I prefer the approach as > >> >> done in the patch below since it doesn't need any new flags and doesn't > >> >> cause any other extra overhead. > >> >> > >> >> [1] https://patchwork.kernel.org/patch/10384261/ > >> >> > >> >> LGTMed-by: Viresh Kumar > >> >> LGTMed-by: Juri Lelli > >> > > >> > Looks like a Tag you just invented ? :) > >> > >> Yeah. > >> > >> The LGTM from Juri can be converned into an ACK silently IMO. That > >> said I have added Looks-good-to: tags to a couple of commits. :-) > > > > Cool, I'll covert them to Acks :-) > > So it looks like I should expect an update of this patch, right? > > Or do you prefer the current one to be applied and work on top of it? Well, sorry, I can't apply this one as it is racy.