cc: Stop using transfer buffer limit for 1-copy rasterizer.

cc: Stop using transfer buffer limit for 1-copy rasterizer.

It doesn't make sense for 1-copy rasterizer where we can
control the exact amount of memory used to be affected
by the transfer buffer limit.

This sets the upper bound to 32 resources, which is reduced
to 0 when invisible. A simple constant like this is likely
what we want long term.

BUG=406404
Committed: https://crrev.com/c84602a0c635053a14fc0e06d4dd0b8e1ce043fa
Cr-Commit-Position: refs/heads/master@{#296423}

[reveman, 2014-09-24 02:02:42]

reveman@chromium.org changed reviewers:
+ danakj@chromium.org, vmpstr@chromium.org

[danakj, 2014-09-24 14:44:38]

LGTM

[danakj, 2014-09-24 14:44:40]

The CQ bit was checked by danakj@chromium.org

[commit-bot: I haz the power, 2014-09-24 14:45:06]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/597833002/1

[commit-bot: I haz the power, 2014-09-24 15:41:31]

Committed patchset #1 (id:1) as dcb4ce339a7a983f03a462e97fff8d33b3e84a95

[commit-bot: I haz the power, 2014-09-24 15:42:13]

Patchset 1 (id:??) landed as
https://crrev.com/c84602a0c635053a14fc0e06d4dd0b8e1ce043fa
Cr-Commit-Position: refs/heads/master@{#296423}