Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752617AbdGGWPz (ORCPT ); Fri, 7 Jul 2017 18:15:55 -0400 Received: from mail.kernel.org ([198.145.29.99]:56182 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750941AbdGGWPy (ORCPT ); Fri, 7 Jul 2017 18:15:54 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 559D422BD8 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=goodmis.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=rostedt@goodmis.org Date: Fri, 7 Jul 2017 18:15:49 -0400 From: Steven Rostedt To: Joel Fernandes Cc: "Rafael J. Wysocki" , Juri Lelli , Thomas Gleixner , Peter Zijlstra , Ingo Molnar , Viresh Kumar , LKML , Linux PM , Vincent Guittot , Luca Abeni , claudio@evidence.eu.com, Tommaso Cucinotta , bristot@redhat.com, Mathieu Poirier , Todd Kjos , Andres Oportus , Morten Rasmussen , Dietmar Eggemann , Patrick Bellasi , Ingo Molnar , "Rafael J . Wysocki" Subject: Re: [RFC PATCH v1 3/8] sched/cpufreq_schedutil: make worker kthread be SCHED_DEADLINE Message-ID: <20170707181549.5ca5cf31@gandalf.local.home> In-Reply-To: References: <20170705085905.6558-1-juri.lelli@arm.com> <20170707105316.whutk3h6x2h6xvyt@e106622-lin> <4582085.aKtjXTl7qR@aspire.rjw.lan> <20170707175805.6bd8f34d@gandalf.local.home> X-Mailer: Claws Mail 3.14.0 (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 597 Lines: 17 On Fri, 7 Jul 2017 15:07:09 -0700 Joel Fernandes wrote: > > It is rather long. Although I actually hate the SUGOV, it is easily > > grepable. Just comment what it stands for. We can always change it > > later. > > I was thinking why not just SCHED_FLAG_CPUFREQ. That says its for > cpufreq purposes, and is a bit self-documenting. "WORKER" is a bit > redundant and can be dropped in my opinion. I was thinking that too, but was wondering how tightly coupled is this with SCHED_DEADLINE? I like the searchability of SUGOV, where as CPUFREQ is still quite broad. -- Steve