Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp1523382ybl; Thu, 5 Dec 2019 02:50:39 -0800 (PST) X-Google-Smtp-Source: APXvYqzVrL0K3CVZEzL19YMzsy5Xzj/nLdbBMzZIs8TU0pMX1m914V/TDOj2IaxlrOe+GO/uORrx X-Received: by 2002:a05:6808:191:: with SMTP id w17mr6339017oic.29.1575543039347; Thu, 05 Dec 2019 02:50:39 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1575543039; cv=none; d=google.com; s=arc-20160816; b=wXZicU+UQUdmMq+FHpfn9rH+x0XBFMUASNwI7oXDPO4YoylRkL45+SaRfwyBtkuyxj o3DeW19KnLM+3ZsL/9XHAHc4P2a+nhOirLMWsM0HNktmFAbKjwSxBv76AakeVZKHH5yk uCPQIN0jSXBiDkMcASeTpm5g+sk7iflKF9ocXu+sNPDNg+x+wPgGTwKA66tv77d5uiek nZEb9jhFr64OGrbo6KW3l58pfWdHY9ohrdUmUMlco3q40E7GFvpWbjMiW+4Kwsioxwz0 8bTM4VEWysyjtd9V45x+wIifWs2NCdn0IIsq78jTt6nESwdPJRKGCdGu13RXnb7PugCj Z9jw== 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 :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=27OlKUqRyYIvGzAg7S7hmEMBmQemjraUwUjLEy3awUg=; b=omxVfYIRQzbtmDexRmwKaoJ7kD7m/7xYECR/btS+e+HVXKG3JHd0kwpecOr/2lSt0p E8H0xL5Ualodv/VuxIxYGHzPYQ+97mJaNmDSn1fSB+2R4TjUwLQunRtI+G2SQnTKipB+ j0SkSN3lttn3CPGjNx/YrAQWaFPmKXZnCmP4bns+8k5a3FzWBsyPgIry+exETIJqZQ1g xeGD/0K8V8QpwITWz926hhLEzj9/eBliPSMxkrlGwfW6PwGssbJ3U+4e8FnEdsFXTS7Z bAc+jeCrSZP05qJs3GLZiCpvD5DXIew4tIhO+YYiSQSItxHv81Eu0uAWimQxV4jW8Rzg A9xQ== 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 k205si1610453oif.246.2019.12.05.02.50.27; Thu, 05 Dec 2019 02:50:39 -0800 (PST) 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 S1729117AbfLEKuB (ORCPT + 99 others); Thu, 5 Dec 2019 05:50:01 -0500 Received: from foss.arm.com ([217.140.110.172]:58226 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729017AbfLEKuB (ORCPT ); Thu, 5 Dec 2019 05:50:01 -0500 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 A576031B; Thu, 5 Dec 2019 02:50:00 -0800 (PST) Received: from [10.1.194.37] (e113632-lin.cambridge.arm.com [10.1.194.37]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 6F30E3F52E; Thu, 5 Dec 2019 02:49:58 -0800 (PST) Subject: Re: [RFC 0/3] Introduce per-task latency_tolerance for scheduler hints To: Dietmar Eggemann , Parth Shah , linux-kernel@vger.kernel.org Cc: peterz@infradead.org, mingo@redhat.com, vincent.guittot@linaro.org, patrick.bellasi@matbug.net, qais.yousef@arm.com, pavel@ucw.cz, dhaval.giani@oracle.com, qperret@qperret.net, David.Laight@ACULAB.COM, morten.rasmussen@arm.com, pjt@google.com, tj@kernel.org, viresh.kumar@linaro.org, rafael.j.wysocki@intel.com, daniel.lezcano@linaro.org References: <20191125094618.30298-1-parth@linux.ibm.com> <450fc7e2-49d5-d809-281f-7d9a99d3e530@arm.com> From: Valentin Schneider Message-ID: Date: Thu, 5 Dec 2019 10:49:57 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: <450fc7e2-49d5-d809-281f-7d9a99d3e530@arm.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 05/12/2019 09:24, Dietmar Eggemann wrote: > On 25/11/2019 10:46, Parth Shah wrote: >> This patch series is based on the discussion started as the "Usecases for >> the per-task latency-nice attribute"[1] >> >> This patch series introduces a new per-task attribute latency_tolerance to >> provide the scheduler hints about the latency requirements of the task. > > I forgot but is there a chance to have this as a per-taskgroup attribute > as well? > Peter argued we should go for task attributes first, and then cgroup/taskgroups later on: https://lore.kernel.org/lkml/20190905083127.GA2332@hirez.programming.kicks-ass.net/