GpuMemoryManager suggests values for renderer Contents Texture Managers' preferred memory limit.

content/common/gpu/gpu_command_buffer_stub.h

Index: content/common/gpu/gpu_command_buffer_stub.h
diff --git a/content/common/gpu/gpu_command_buffer_stub.h b/content/common/gpu/gpu_command_buffer_stub.h
index 4f0881843804ef595e2d5134e51ad731b03c34ea..009bc5830673d03ce763bb9b1a32fce4319d19d8 100644
--- a/content/common/gpu/gpu_command_buffer_stub.h
+++ b/content/common/gpu/gpu_command_buffer_stub.h
@@ -57,6 +57,7 @@ class CONTENT_EXPORT GpuCommandBufferStubBase {
   virtual ~GpuCommandBufferStubBase() {}
 
   // Will not have surface state if this is an offscreen commandbuffer.
+  virtual bool handles_memory_allocations() const = 0;

[nduca, 2012/04/23 22:12:18]

bikeshed man wonders if "client responds to" or "client listens to" would be
more effective here. Or client_has_memory_allocation_changed_callback... then
its super precise.

   virtual bool has_surface_state() const = 0;
   virtual const SurfaceState& surface_state() const = 0;
 
@@ -107,6 +108,9 @@ class GpuCommandBufferStub
   virtual bool Send(IPC::Message* msg) OVERRIDE;
 
   // GpuCommandBufferStubBase implementation:
+  bool handles_memory_allocations() const OVERRIDE {
+    return handles_memory_allocations_;
+  }
   virtual bool has_surface_state() const OVERRIDE;
   virtual const GpuCommandBufferStubBase::SurfaceState& surface_state() const
       OVERRIDE;
@@ -198,6 +202,8 @@ class GpuCommandBufferStub
   void OnDiscardBackbuffer();
   void OnEnsureBackbuffer();
 
+  void OnHandlesMemoryAllocations();
+
   void OnReschedule();
 
   void OnCommandProcessed();
@@ -221,6 +227,7 @@ class GpuCommandBufferStub
   gfx::GpuPreference gpu_preference_;
   int32 route_id_;
   bool software_;
+  bool handles_memory_allocations_;
   uint32 last_flush_count_;
   scoped_ptr<GpuCommandBufferStubBase::SurfaceState> surface_state_;
   GpuMemoryAllocation allocation_;