Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 431c7a74 authored by lihaizhou's avatar lihaizhou Committed by haizhou li
Browse files

Remove set_cpuset_policy due to new taskprofiles for SF threads 



Now that we have this CL
(Change-Id: I6746e768fbf850202f2008f5e2131326e3a8f6a8)
SurfaceFlinger: add custom taskprofiles for SF threads

Maybe it's time we got rid of the old interface #set_cpuset_policy
Because the old interface gonna be covered and it can be confusing.

Bug: 267383322
Test: Remove this line of code or changing to something else like
 SP_FOREGROUND,it won't make any real difference.
Change-Id: Icaedeb17ddf2b14a5113ea84da0bb4e17d4abd74
Signed-off-by: default avatarlihaizhou <lihaizhou@coolpad.com>
parent 7f623a39

services/surfaceflinger/main_surfaceflinger.cpp

+0 −5
Original line number Diff line number Diff line
@@ -139,11 +139,6 @@ int main(int, char**) { 


    set_sched_policy(0, SP_FOREGROUND);



    // Put most SurfaceFlinger threads in the system-background cpuset

    // Keeps us from unnecessarily using big cores

    // Do this after the binder thread pool init

    if (cpusets_enabled()) set_cpuset_policy(0, SP_SYSTEM);



    // initialize before clients can connect

    flinger->init();