On Tue, May 7, 2013 at 4:24 AM, Eric Anholt wrote:
> Paul Berry writes:
>
>> Currently the i965 driver uses a single buffer object to hold both batch
>> buffer commands and dynamic state data structures (which are pointed to by
>> batch buffer commands). We use a "stack and heap model", where th
>> What do you think?
>
> It would need some sort of plan for how to deal with making
> drm_intel_bufmgr_check_aperture work correctly and efficiently when a
> reloced-to BO gets new relocs, which is the reason everything is in one
> BO currently.
I was looking for code that did this for something
Paul Berry writes:
> Currently the i965 driver uses a single buffer object to hold both batch
> buffer commands and dynamic state data structures (which are pointed to by
> batch buffer commands). We use a "stack and heap model", where the former
> are allocated from the front end of the bo and
Currently the i965 driver uses a single buffer object to hold both batch
buffer commands and dynamic state data structures (which are pointed to by
batch buffer commands). We use a "stack and heap model", where the former
are allocated from the front end of the bo and the latter are allocated
from
