gpu: GPU service scheduler.

gpu/command_buffer/common/gpu_stream_constants.h

 // Copyright 2015 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #ifndef GPU_IPC_COMMON_GPU_STREAM_CONSTANTS_H_
 #define GPU_IPC_COMMON_GPU_STREAM_CONSTANTS_H_
 
+#include "gpu/gpu_export.h"
+
 namespace gpu {
 
-enum class GpuStreamPriority { REAL_TIME, HIGH, NORMAL, LOW, LAST = LOW };
+enum class GpuStreamPriority : int { REAL_TIME, HIGH, NORMAL, LOW, LAST = LOW };
+static const int kNumGpuStreamPriorities = 4;
 
-enum GpuStreamId { GPU_STREAM_DEFAULT = -1, GPU_STREAM_INVALID = 0 };
+enum GpuStreamId {
+  GPU_STREAM_INVALID = -1,
+  GPU_STREAM_DEFAULT = 0,
+  GPU_STREAM_WORKER = 1,

[piman, 2017/05/09 00:48:38]

I'm not excited about defining here a notion that belongs to the higher levels
(worker). For example we may decide in the future that we want a separate stream
for Pepper or WebGL or video, but those are concepts that only exist in content/

I would prefer keeping that enum in content/, if we want a static allocation of
stream ids. Otherwise the previous dynamic allocation doesn't seem all that
bothersome?

[sunnyps, 2017/05/10 23:15:15]

The service side implementation of stream lifetimes is simpler for static
allocation of streams. The service doesn't need to specifically know the stream
ids so I've moved those to content/common/gpu_stream_constants.h.

+};
+
+GPU_EXPORT const char* GpuStreamPriorityToString(GpuStreamPriority priority);
 
 }  // namespace gpu
 
 #endif  // GPU_IPC_COMMON_GPU_STREAM_CONSTANTS_H_