Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752599AbdGGW5c (ORCPT ); Fri, 7 Jul 2017 18:57:32 -0400 Received: from mail-oi0-f44.google.com ([209.85.218.44]:36374 "EHLO mail-oi0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751100AbdGGW5a (ORCPT ); Fri, 7 Jul 2017 18:57:30 -0400 MIME-Version: 1.0 In-Reply-To: <20170707181549.5ca5cf31@gandalf.local.home> References: <20170705085905.6558-1-juri.lelli@arm.com> <20170707105316.whutk3h6x2h6xvyt@e106622-lin> <4582085.aKtjXTl7qR@aspire.rjw.lan> <20170707175805.6bd8f34d@gandalf.local.home> <20170707181549.5ca5cf31@gandalf.local.home> From: Joel Fernandes Date: Fri, 7 Jul 2017 15:57:28 -0700 Message-ID: Subject: Re: [RFC PATCH v1 3/8] sched/cpufreq_schedutil: make worker kthread be SCHED_DEADLINE To: Steven Rostedt 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" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 807 Lines: 23 On Fri, Jul 7, 2017 at 3:15 PM, Steven Rostedt wrote: > 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. Yes this is tightly coupled with DL so in that case probably a more specific name is better as you mentioned. thanks, -Joel