Add category handling to RasterWorkerPool

content/public/common/content_switches.h

Index: content/public/common/content_switches.h
diff --git a/content/public/common/content_switches.h b/content/public/common/content_switches.h
index 45297bbff9ab2cb5b17de77415513aba94fea124..17de5d51676ea17b01bc7cb7cc20cabd6b35768c 100644
--- a/content/public/common/content_switches.h
+++ b/content/public/common/content_switches.h
@@ -232,6 +232,7 @@ CONTENT_EXPORT extern const char kVideoImageTextureTarget[];
 CONTENT_EXPORT extern const char kUseMobileUserAgent[];
 CONTENT_EXPORT extern const char kUseNormalPriorityForTileTaskWorkerThreads[];
 CONTENT_EXPORT extern const char kUseRemoteCompositing[];
+CONTENT_EXPORT extern const char kUseSingleThreadForBackgroundRasterTasks[];

[reveman, 2016/01/13 23:09:30]

nit: Remove "Raster" as this technically not limited to raster tasks.

However, I don't think we need a flag for this. Even if we haven't been able to
demonstrate a huge benefit yet I think it makes sense to always use this. I'm
expecting the benefit to come from increasing the number of raster threads
without the regression in responsiveness that we've seen in the past.

[ericrk, 2016/01/21 01:19:44]

Fair enough - we can see what happens when we land this without the flag.

 extern const char kUseSurfaces[];
 CONTENT_EXPORT extern const char kDisableSurfaces[];
 extern const char kUtilityCmdPrefix[];