On Wed, Jan 8, 2014 at 7:54 PM, Lauri Kasanen wrote:
> On Wed, 8 Jan 2014 19:03:53 +0100
> Marek Olšák wrote:
>
>> On Wed, Jan 8, 2014 at 6:21 PM, Lauri Kasanen wrote:
>> > On Wed, 8 Jan 2014 15:54:04 +0100
>> > Marek Olšák wrote:
>> >> It's not accurate at all, it's actually pretty random. The
On Wed, 8 Jan 2014 19:03:53 +0100
Marek Olšák wrote:
> On Wed, Jan 8, 2014 at 6:21 PM, Lauri Kasanen wrote:
> > On Wed, 8 Jan 2014 15:54:04 +0100
> > Marek Olšák wrote:
> >> It's not accurate at all, it's actually pretty random. The stats
> >> should not be called "num_reads" and "num_writes",
On Wed, Jan 8, 2014 at 6:38 PM, Lauri Kasanen wrote:
> On Wed, 8 Jan 2014 15:56:33 +0200
> Lauri Kasanen wrote:
>
>> On Wed, 8 Jan 2014 12:03:12 +0100
>> Marek Olšák wrote:
>> > Also, last_cpu_time will be wrong anyway, because the driver may call
>> > the buffer_map function only once per buffe
On Wed, Jan 8, 2014 at 6:21 PM, Lauri Kasanen wrote:
> On Wed, 8 Jan 2014 15:54:04 +0100
> Marek Olšák wrote:
>
>> > On Wed, 8 Jan 2014 12:03:12 +0100
>> > Marek Olšák wrote:
>> >> Why don't you just set the statistics once per CS in
>> >> radeon_drm_cs_flush? I don't see a value in doing it in
On Wed, 8 Jan 2014 15:56:33 +0200
Lauri Kasanen wrote:
> On Wed, 8 Jan 2014 12:03:12 +0100
> Marek Olšák wrote:
> > Also, last_cpu_time will be wrong anyway, because the driver may call
> > the buffer_map function only once per buffer, e.g. at buffer creation.
> > It's not a rule, but it happens
On Wed, 8 Jan 2014 15:54:04 +0100
Marek Olšák wrote:
> > On Wed, 8 Jan 2014 12:03:12 +0100
> > Marek Olšák wrote:
> >> Why don't you just set the statistics once per CS in
> >> radeon_drm_cs_flush? I don't see a value in doing it in every function
> >> that sets the resources.
> >
> > It's the o
On Wed, Jan 8, 2014 at 2:56 PM, Lauri Kasanen wrote:
> On Wed, 8 Jan 2014 12:03:12 +0100
> Marek Olšák wrote:
>
>> On Tue, Jan 7, 2014 at 7:14 PM, Lauri Kasanen wrote:
>> > These will be used later on for optimizing the VRAM placement.
>> >
>> > No measurable overhead (glxgears, torcs).
>> >
>>
On Wed, 8 Jan 2014 12:03:12 +0100
Marek Olšák wrote:
> On Tue, Jan 7, 2014 at 7:14 PM, Lauri Kasanen wrote:
> > These will be used later on for optimizing the VRAM placement.
> >
> > No measurable overhead (glxgears, torcs).
> >
> > v2: Get accurate stats by taking dirty_masks into account
>
>
On Tue, Jan 7, 2014 at 7:14 PM, Lauri Kasanen wrote:
> These will be used later on for optimizing the VRAM placement.
>
> No measurable overhead (glxgears, torcs).
>
> v2: Get accurate stats by taking dirty_masks into account
Why don't you just set the statistics once per CS in
radeon_drm_cs_flus
These will be used later on for optimizing the VRAM placement.
No measurable overhead (glxgears, torcs).
v2: Get accurate stats by taking dirty_masks into account
Marek: I'm not sure I was testing torcs right; I started a race on Forza, drove
around, and looked at the fps. Doesn't seem to do ti
On Tue, Jan 7, 2014 at 11:14 AM, Lauri Kasanen wrote:
> On Tue, 7 Jan 2014 01:44:28 +0100
> Marek Olšák wrote:
>
>> On Mon, Jan 6, 2014 at 12:17 PM, Lauri Kasanen wrote:
>> > These will be used later on for optimizing the VRAM placement.
>> >
>> > No measurable overhead (glxgears).
>>
>> I recom
On Tue, 7 Jan 2014 01:44:28 +0100
Marek Olšák wrote:
> On Mon, Jan 6, 2014 at 12:17 PM, Lauri Kasanen wrote:
> > These will be used later on for optimizing the VRAM placement.
> >
> > No measurable overhead (glxgears).
>
> I recommend testing torcs (the Forza track) next time. glxgears is not
>
On Mon, Jan 6, 2014 at 12:17 PM, Lauri Kasanen wrote:
> These will be used later on for optimizing the VRAM placement.
>
> No measurable overhead (glxgears).
I recommend testing torcs (the Forza track) next time. glxgears is not
useful here.
>
> Signed-off-by: Lauri Kasanen
> ---
> src/gallium
These will be used later on for optimizing the VRAM placement.
No measurable overhead (glxgears).
Signed-off-by: Lauri Kasanen
---
src/gallium/winsys/radeon/drm/radeon_drm_bo.c | 3 +++
src/gallium/winsys/radeon/drm/radeon_drm_bo.h | 16
src/gallium/winsys/radeon/drm/radeon_dr
These will be used later on for optimizing the VRAM placement.
No measurable overhead (glxgears).
Signed-off-by: Lauri Kasanen
---
src/gallium/winsys/radeon/drm/radeon_drm_bo.c | 3 +++
src/gallium/winsys/radeon/drm/radeon_drm_bo.h | 16
src/gallium/winsys/radeon/drm/radeon_dr
These will be used later on for optimizing the VRAM placement.
Currently some glxgears overhead (~7% less), real apps yet to be benched.
Signed-off-by: Lauri Kasanen
---
src/gallium/winsys/radeon/drm/radeon_drm_bo.c | 3 +++
src/gallium/winsys/radeon/drm/radeon_drm_bo.h | 16
s
16 matches
Mail list logo
