[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181107121126.GN9781@hirez.programming.kicks-ass.net>
Date: Wed, 7 Nov 2018 13:11:26 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Patrick Bellasi <patrick.bellasi@....com>
Cc: linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org,
Ingo Molnar <mingo@...hat.com>, Tejun Heo <tj@...nel.org>,
"Rafael J . Wysocki" <rafael.j.wysocki@...el.com>,
Vincent Guittot <vincent.guittot@...aro.org>,
Viresh Kumar <viresh.kumar@...aro.org>,
Paul Turner <pjt@...gle.com>,
Quentin Perret <quentin.perret@....com>,
Dietmar Eggemann <dietmar.eggemann@....com>,
Morten Rasmussen <morten.rasmussen@....com>,
Juri Lelli <juri.lelli@...hat.com>,
Todd Kjos <tkjos@...gle.com>,
Joel Fernandes <joelaf@...gle.com>,
Steve Muckle <smuckle@...gle.com>,
Suren Baghdasaryan <surenb@...gle.com>,
linux-api@...r.kernel.org
Subject: Re: [PATCH v5 02/15] sched/core: make sched_setattr able to tune the
current policy
On Mon, Oct 29, 2018 at 06:32:56PM +0000, Patrick Bellasi wrote:
> @@ -50,11 +52,13 @@
> #define SCHED_FLAG_RESET_ON_FORK 0x01
> #define SCHED_FLAG_RECLAIM 0x02
> #define SCHED_FLAG_DL_OVERRUN 0x04
> -#define SCHED_FLAG_UTIL_CLAMP 0x08
> +#define SCHED_FLAG_TUNE_POLICY 0x08
> +#define SCHED_FLAG_UTIL_CLAMP 0x10
That seems to suggest you want to do this patch first, but you didn't..
Powered by blists - more mailing lists