On Mon, Dec 10, 2012 at 3:16 PM, Jerome Glisse wrote:
> On Thu, Nov 29, 2012 at 10:35 AM, wrote:
>> From: Jerome Glisse
>>
>> The bo creation placement is where the bo will be. Instead of trying
>> to move bo at each command stream let this work to another worker
>> thread that will use more ad
On Mon, Dec 10, 2012 at 3:16 PM, Jerome Glisse wrote:
> On Thu, Nov 29, 2012 at 10:35 AM, wrote:
>> From: Jerome Glisse
>>
>> The bo creation placement is where the bo will be. Instead of trying
>> to move bo at each command stream let this work to another worker
>> thread that will use more ad
On Thu, Nov 29, 2012 at 10:35 AM, wrote:
> From: Jerome Glisse
>
> The bo creation placement is where the bo will be. Instead of trying
> to move bo at each command stream let this work to another worker
> thread that will use more advance heuristic.
>
> Signed-off-by: Jerome Glisse
What about
On Thu, Nov 29, 2012 at 10:35 AM, wrote:
> From: Jerome Glisse
>
> The bo creation placement is where the bo will be. Instead of trying
> to move bo at each command stream let this work to another worker
> thread that will use more advance heuristic.
>
> Signed-off-by: Jerome Glisse
What about
From: Jerome Glisse
The bo creation placement is where the bo will be. Instead of trying
to move bo at each command stream let this work to another worker
thread that will use more advance heuristic.
Signed-off-by: Jerome Glisse
---
drivers/gpu/drm/radeon/radeon.h| 1 +
drivers/gpu/dr
From: Jerome Glisse
The bo creation placement is where the bo will be. Instead of trying
to move bo at each command stream let this work to another worker
thread that will use more advance heuristic.
Signed-off-by: Jerome Glisse
---
drivers/gpu/drm/radeon/radeon.h| 1 +
drivers/gpu/dr
