接上篇cpuset，這篇來看看進程優(yōu)先級與調度策略管理。
一、進程優(yōu)先級與調度策略
Linux中，優(yōu)先級號一共有0-139，其中0-99的是RT（實時）進程，100-139的是非實時進程。
數(shù)字越低優(yōu)先級越高。
實時調度：針對0-99的RT進程
- SCHED_FIFO：不同優(yōu)先級的高的先跑，相同優(yōu)先級的先來先跑，一旦占據CPU就要到跑完為止。
- SCHED_RR：不同優(yōu)先級的高的先跑，相同優(yōu)先級的時間片輪詢。
分時調度：針對100-139的普通進程，他們按nice值 -20 - 19來算優(yōu)先級，越nice優(yōu)先級越低
- SCHED_NOMAL（SCHED_OTHER）：時間片輪詢，優(yōu)先級越高搶占能力越強，越容易獲得更多時間片。
- SCHED_BATCH 批處理進程，喚醒不頻繁的使用SCHED_BATCH，頻繁的適合SCHED_NOMAL。
SCHED_IDLE idle狀態(tài)低優(yōu)先級進程調度
二、調度策略與優(yōu)先級設置
frameworks/base/core/java/android/os/Process.java
public static final int SCHED_OTHER = 0;
public static final int SCHED_FIFO = 1;
public static final int SCHED_RR = 2;
public static final int SCHED_BATCH = 3;
public static final int SCHED_IDLE = 5;
先看Process中調度策略的劃分，與上面介紹的一樣。
frameworks/base/services/core/java/com/android/server/am/ActivityManagerService.java
static boolean scheduleAsRegularPriority(int tid, boolean suppressLogs) {
try {
Process.setThreadScheduler(tid, Process.SCHED_OTHER, 0);
return true;
} catch (IllegalArgumentException e) {
if (!suppressLogs) {
Slog.w(TAG, "Failed to set scheduling policy, thread does not exist:\n" + e);
}
}
return false;
}
static boolean scheduleAsFifoPriority(int tid, boolean suppressLogs) {
try {
Process.setThreadScheduler(tid, Process.SCHED_FIFO | Process.SCHED_RESET_ON_FORK, 1);
return true;
} catch (IllegalArgumentException e) {
if (!suppressLogs) {
Slog.w(TAG, "Failed to set scheduling policy, thread does not exist:\n" + e);
}
}
return false;
}
首先在AMS中封裝了FIFO和NORMAL的兩個策略，NORMAL好說，看看FIFO在哪用到
private final boolean applyOomAdjLocked(ProcessRecord app, boolean doingAll, long now,
long nowElapsed) {
…
setProcessGroup(app.pid, processGroup); //這里上篇文章已經講過了
if (app.curSchedGroup == ProcessList.SCHED_GROUP_TOP_APP) {
// do nothing if we already switched to RT
if (oldSchedGroup != ProcessList.SCHED_GROUP_TOP_APP) {
mVrController.onTopProcChangedLocked(app);
//UI渲染使用的fifo，但是mUseFifoUiScheduling條件需要打開：
//if (SystemProperties.getInt("sys.use_fifo_ui", 0) != 0) {
// mUseFifoUiScheduling = true;
// }
但是getprop看了下，壓根就沒有設置，那就是并沒有使用到fifo策略，可能也并沒有什么優(yōu)化效果吧。
if (mUseFifoUiScheduling) {
// Switch UI pipeline for app to SCHED_FIFO
app.savedPriority = Process.getThreadPriority(app.pid);
scheduleAsFifoPriority(app.pid, /* suppressLogs */true);
if (app.renderThreadTid != 0) {
scheduleAsFifoPriority(app.renderThreadTid,
/* suppressLogs */true);
if (DEBUG_OOM_ADJ) {
Slog.d("UI_FIFO", "Set RenderThread (TID " +
app.renderThreadTid + ") to FIFO");
}
} else {
if (DEBUG_OOM_ADJ) {
Slog.d("UI_FIFO", "Not setting RenderThread TID");
}
}
} else {//如果不調整，那么直接就設置優(yōu)先級。
// Boost priority for top app UI and render threads
setThreadPriority(app.pid, TOP_APP_PRIORITY_BOOST);
if (app.renderThreadTid != 0) {
try {
setThreadPriority(app.renderThreadTid,
TOP_APP_PRIORITY_BOOST);
} catch (IllegalArgumentException e) {
// thread died, ignore
}
}
}
}
}
...
}
這里Process.setThreadScheduler并沒有太多的應用，我們直接來看優(yōu)先級設置吧。else中將top app的UI線程與render線程都設置為TOP_APP_PRIORITY_BOOST優(yōu)先級，nice值為-10，非常高。
frameworks/base/core/java/android/os/Process.java
public static final int THREAD_PRIORITY_DEFAULT = 0;
public static final int THREAD_PRIORITY_LOWEST = 19;
public static final int THREAD_PRIORITY_BACKGROUND = 10;
public static final int THREAD_PRIORITY_FOREGROUND = -2;
public static final int THREAD_PRIORITY_DISPLAY = -4;
public static final int THREAD_PRIORITY_URGENT_DISPLAY = -8;
public static final int THREAD_PRIORITY_AUDIO = -16;
public static final int THREAD_PRIORITY_URGENT_AUDIO = -19;
public static final int THREAD_PRIORITY_MORE_FAVORABLE = -1;
public static final int THREAD_PRIORITY_LESS_FAVORABLE = +1;
而TOP_APP_PRIORITY_BOOST=-10 定義在AMS中。
public static final native void setThreadPriority(int priority)
throws IllegalArgumentException, SecurityException;
setThreadPriority在Process中是native方法，那直接jni進去
frameworks/base/core/jni/android_util_Process.cpp
void android_os_Process_setThreadPriority(JNIEnv* env, jobject clazz,
jint pid, jint pri)
{
#if GUARD_THREAD_PRIORITY
// if we're putting the current thread into the background, check the TLS
// to make sure this thread isn't guarded. If it is, raise an exception.
if (pri >= ANDROID_PRIORITY_BACKGROUND) {
if (pid == gettid()) {
void* bgOk = pthread_getspecific(gBgKey);
if (bgOk == ((void*)0xbaad)) {
ALOGE("Thread marked fg-only put self in background!");
jniThrowException(env, "java/lang/SecurityException", "May not put this thread into background");
return;
}
}
}
#endif
int rc = androidSetThreadPriority(pid, pri);//設置thread優(yōu)先級
if (rc != 0) {
if (rc == INVALID_OPERATION) {
signalExceptionForPriorityError(env, errno, pid);
} else {
signalExceptionForGroupError(env, errno, pid);
}
}
//ALOGI("Setting priority of %" PRId32 ": %" PRId32 ", getpriority returns %d\n",
// pid, pri, getpriority(PRIO_PROCESS, pid));
}
這里主要調用androidSetThreadPriority方法
system/core/libutils/Threads.cpp
int androidSetThreadPriority(pid_t tid, int pri)
{
int rc = 0;
int lasterr = 0;
//如果priority大于等于BACKGROUND，則設置為BACKGROUND類型的調度策略
if (pri >= ANDROID_PRIORITY_BACKGROUND) {
rc = set_sched_policy(tid, SP_BACKGROUND);
//如果priority小于BACKGROUND，且當線程為BACKGROUND類型，則設置為FOREGROUND類型。
} else if (getpriority(PRIO_PROCESS, tid) >= ANDROID_PRIORITY_BACKGROUND) {
rc = set_sched_policy(tid, SP_FOREGROUND);
}
if (rc) {
lasterr = errno;
}
if (setpriority(PRIO_PROCESS, tid, pri) < 0) {//這里最終設置優(yōu)先級
rc = INVALID_OPERATION;
} else {
errno = lasterr;
}
return rc;
}
這里通過set_sched_policy來調整調度策略，并通過setpriority設置進程優(yōu)先級。這里不特意區(qū)分進程與線程了，反正在linux中都是進程。
system/core/libcutils/sched_policy.cpp
int set_sched_policy(int tid, SchedPolicy policy)
{
if (tid == 0) {
tid = gettid();
}
policy = _policy(policy);
pthread_once(&the_once, __initialize);
#if POLICY_DEBUG
char statfile[64];
char statline[1024];
char thread_name[255];
snprintf(statfile, sizeof(statfile), "/proc/%d/stat", tid);
memset(thread_name, 0, sizeof(thread_name));
int fd = open(statfile, O_RDONLY | O_CLOEXEC);
if (fd >= 0) {
int rc = read(fd, statline, 1023);
close(fd);
statline[rc] = 0;
char *p = statline;
char *q;
for (p = statline; *p != '('; p++);
p++;
for (q = p; *q != ')'; q++);
strncpy(thread_name, p, (q-p));
}
switch (policy) {
case SP_BACKGROUND:
SLOGD("vvv tid %d (%s)", tid, thread_name);
break;
case SP_FOREGROUND:
case SP_AUDIO_APP:
case SP_AUDIO_SYS:
case SP_TOP_APP:
SLOGD("^^^ tid %d (%s)", tid, thread_name);
break;
case SP_SYSTEM:
SLOGD("http:/// tid %d (%s)", tid, thread_name);
break;
default:
SLOGD("??? tid %d (%s)", tid, thread_name);
break;
}
#endif
if (schedboost_enabled()) {
int boost_fd = -1;
switch (policy) {
case SP_BACKGROUND:
boost_fd = bg_schedboost_fd;
break;
case SP_FOREGROUND:
case SP_AUDIO_APP:
case SP_AUDIO_SYS:
boost_fd = fg_schedboost_fd;
break;
case SP_TOP_APP:
boost_fd = ta_schedboost_fd;
break;
default:
boost_fd = -1;
break;
}
//add_tid_to_cgroup又繼續(xù)寫節(jié)點
if (boost_fd > 0 && add_tid_to_cgroup(tid, boost_fd) != 0) {
if (errno != ESRCH && errno != ENOENT)
return -errno;
}
}
//timerslack是個睡眠策略，就是至少要睡這么長時間才能醒來，屬于省電方面的優(yōu)化策略
if (__sys_supports_timerslack) {
set_timerslack_ns(tid, policy == SP_BACKGROUND ?
TIMER_SLACK_BG : TIMER_SLACK_FG);
}
return 0;
}
這里與前面的cpuset非常相似，依然是寫節(jié)點，節(jié)點前面也提了就是：
if (schedboost_enabled()) {//這里對應的是sched路徑
filename = "/dev/stune/top-app/tasks";
ta_schedboost_fd = open(filename, O_WRONLY | O_CLOEXEC);
filename = "/dev/stune/foreground/tasks";
fg_schedboost_fd = open(filename, O_WRONLY | O_CLOEXEC);
filename = "/dev/stune/background/tasks";
bg_schedboost_fd = open(filename, O_WRONLY | O_CLOEXEC);
}
那么這里又引入了一個schedtune子系統(tǒng)，簡單介紹下：
schedtune是ARM/Linaro為了EAS新增的一個子系統(tǒng)，主要用來控制進程調度選擇CPU以及boost觸發(fā)。通過權重來分配CPU負載能力來實現(xiàn)快速運行。高權重意味著會享受到更好的cpu負載來處理對應的任務，換句話說你能享受相對更好的cpu運行性能。
簡單梳理下schedtune和不同類型SchedPolicy之間的對應關系：
/dev/stune/top-app/tasks SP_TOP_APP
/dev/stune/foreground/tasks SP_FOREGROUND
/dev/stune/background/tasks SP_BACKGROUND
看下具體文件夾內容：
/dev/stune/top-app # ls -al
total 0
drwxr-xr-x 2 system system 0 1970-05-22 03:35 .
dr-xr-xr-x 7 system system 0 1970-05-22 03:35 ..
-rw-r--r-- 1 root root 0 2019-08-17 18:06 cgroup.clone_children
-rw-r--r-- 1 root root 0 2019-08-17 18:06 cgroup.procs
-rw-r--r-- 1 root root 0 2019-08-17 18:06 notify_on_release
-rw-r--r-- 1 root root 0 2019-08-12 13:41 schedtune.boost
-rw-r--r-- 1 root root 0 1970-05-22 03:35 schedtune.colocate
-rw-r--r-- 1 root root 0 2019-08-12 13:41 schedtune.prefer_idle
-rw-r--r-- 1 root root 0 1970-05-22 03:35 schedtune.sched_boost_no_override
-rw-rw-r-- 1 system system 0 1970-05-22 03:35 tasks
系統(tǒng)配置：
這里/dev/stune相關配置只做了這么一個
# choose idle CPU for top app tasks
echo 1 > /dev/stune/top-app/schedtune.prefer_idle
