Step 1: Changing CommandBufferHelper to only use a portion

of the command buffer. This brought out the fact that
there were lots of places in the code mixing size in bytes
with num command buffer entries.

This fixes most of those issues. No public interface
uses num command buffer entries except 
gpu::CommandBuffer::State where it makes sense.

TEST=relying on unit tests, conformance tests and chrome
BUG=none

Review URL: http://codereview.chromium.org/2008014

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@47041 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 3 insertions, 4 deletions

diff --git a/gpu/command_buffer/common/command_buffer.h b/gpu/command_buffer/common/command_buffer.h
index 106d9b3..41eda77 100644
--- a/gpu/command_buffer/common/command_buffer.h
+++ b/gpu/command_buffer/common/command_buffer.h
@@ -19,7 +19,7 @@ class CommandBuffer {
 
   struct State {
     State()
-        : size(0),
+        : num_entries(0),
           get_offset(0),
           put_offset(0),
           token(-1),
@@ -27,7 +27,7 @@ class CommandBuffer {
     }
 
     // Size of the command buffer in command buffer entries.
-    int32 size;
+    int32 num_entries;
 
     // The offset (in entries) from which the reader is reading.
     int32 get_offset;
@@ -52,8 +52,7 @@ class CommandBuffer {
   virtual ~CommandBuffer() {
   }
 
-  // Initialize the command buffer with the given size (number of command
-  // entries).
+  // Initialize the command buffer with the given size.
   virtual bool Initialize(int32 size) = 0;
 
   // Gets the ring buffer for the command buffer.