From: Martijn Coenen <maco@android.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: "Greg KH" <gregkh@linuxfoundation.org>,
"John Stultz" <john.stultz@linaro.org>,
"Todd Kjos" <tkjos@google.com>,
"Arve Hjønnevåg" <arve@android.com>,
"Sherry Yang" <sherryy@android.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Amit Pundir" <amit.pundir@linaro.org>,
LKML <linux-kernel@vger.kernel.org>,
devel@driverdev.osuosl.org, "Martijn Coenen" <maco@google.com>
Subject: Re: [PATCH v3 2/6] ANDROID: binder: add min sched_policy to node.
Date: Thu, 16 Nov 2017 10:27:48 +0100 [thread overview]
Message-ID: <CAB0TPYFf3XaaxsnwaQ3CD-AWcyxkfDFwSQM7L6+1Bq2Q8i5NLg@mail.gmail.com> (raw)
In-Reply-To: <20171115130210.y37o3bpyqoo6jgzb@hirez.programming.kicks-ass.net>
On Wed, Nov 15, 2017 at 2:02 PM, Peter Zijlstra <peterz@infradead.org> wrote:
>> 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.
I mostly used these because it makes it easier to debug, since that
range is used in other places in the kernel (and in trace events). All
priority calculations use things that are in sched headers, like
NICE_TO_PRIO, PRIO_TO_NICE, and MAX_USER_RT_PRIO. So things wouldn't
necessarily break if you just changed the value ranges. If you
inverted the range, that would be a problem...
next prev parent reply other threads:[~2017-11-16 9:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-26 14:07 [PATCH v3 0/6] ANDROID: binder: RT priority inheritance Martijn Coenen
2017-10-26 14:07 ` [PATCH v3 1/6] ANDROID: binder: add support for RT prio inheritance Martijn Coenen
2017-11-15 13:01 ` Peter Zijlstra
2017-11-16 9:18 ` Martijn Coenen
2017-11-16 11:27 ` Peter Zijlstra
2017-11-16 13:03 ` Martijn Coenen
2017-11-16 15:10 ` Peter Zijlstra
2017-11-17 10:23 ` Martijn Coenen
2017-10-26 14:07 ` [PATCH v3 2/6] ANDROID: binder: add min sched_policy to node Martijn Coenen
2017-11-15 13:02 ` Peter Zijlstra
2017-11-16 9:27 ` Martijn Coenen [this message]
2017-10-26 14:07 ` [PATCH v3 3/6] ANDROID: binder: improve priority inheritance Martijn Coenen
2017-11-15 13:03 ` Peter Zijlstra
2017-11-16 9:31 ` Martijn Coenen
2017-10-26 14:07 ` [PATCH v3 4/6] ANDROID: binder: add RT inheritance flag to node Martijn Coenen
2017-11-15 13:05 ` Peter Zijlstra
2017-11-16 9:37 ` Martijn Coenen
2017-10-26 14:07 ` [PATCH v3 5/6] ANDROID: binder: don't check prio permissions on restore Martijn Coenen
2017-11-15 13:08 ` Peter Zijlstra
2017-10-26 14:07 ` [PATCH v3 6/6] ANDROID: binder: Add tracing for binder priority inheritance Martijn Coenen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAB0TPYFf3XaaxsnwaQ3CD-AWcyxkfDFwSQM7L6+1Bq2Q8i5NLg@mail.gmail.com \
--to=maco@android.com \
--cc=amit.pundir@linaro.org \
--cc=arve@android.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maco@google.com \
--cc=peterz@infradead.org \
--cc=sherryy@android.com \
--cc=tglx@linutronix.de \
--cc=tkjos@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.