[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171115130210.y37o3bpyqoo6jgzb@hirez.programming.kicks-ass.net>
Date: Wed, 15 Nov 2017 14:02:10 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Martijn Coenen <maco@...roid.com>
Cc: gregkh@...uxfoundation.org, john.stultz@...aro.org,
tkjos@...gle.com, arve@...roid.com, sherryy@...roid.com,
tglx@...utronix.de, amit.pundir@...aro.org,
linux-kernel@...r.kernel.org, devel@...verdev.osuosl.org,
maco@...gle.com
Subject: Re: [PATCH v3 2/6] ANDROID: binder: add min sched_policy to node.
On Thu, Oct 26, 2017 at 04:07:46PM +0200, Martijn Coenen wrote:
> This change adds flags to flat_binder_object.flags
> to allow indicating a minimum scheduling policy for
> the node. It also clarifies the valid value range
> for the priority bits in the flags.
>
> Internally, we use the priority map that the kernel
> uses, e.g. [0..99] for real-time policies and [100..139]
> for the SCHED_NORMAL/SCHED_BATCH policies.
I will break that without consideration if I have to. That really isn't
something anybody outside of the core code should rely on.
Powered by blists - more mailing lists