Explanation of the changes, as requested by Tom Stellard:
Let's take need after is calculated as
item->size_in_dw+2048 - (pool->size_in_dw - allocated)
BEFORE:
If need is positive or 0:
we calculate need += 1024 - (need % 1024), which is like
cealing to the nearest multiple of 1024, f
On Sat, Jan 04, 2014 at 10:25:52PM +0100, Bruno Jimenez wrote:
> On Sat, 2014-01-04 at 13:08 -0800, Tom Stellard wrote:
>
> [snip]
>
> > >
> > > So, you were wright, I changed the behaviour for
> > > need == 0. But just checking for need < 0 should
> > > address it.
> > >
> >
> > Thanks for the
On Sat, Jan 04, 2014 at 06:28:27PM +0100, Bruno Jimenez wrote:
> On Sat, 2014-01-04 at 08:52 -0800, Tom Stellard wrote:
> > On Sat, Jan 04, 2014 at 01:27:32AM +0100, Bruno Jiménez wrote:
> > > ---
> > > src/gallium/drivers/r600/compute_memory_pool.c | 18 +++---
> > > 1 file changed, 7
On Sat, 2014-01-04 at 08:52 -0800, Tom Stellard wrote:
> On Sat, Jan 04, 2014 at 01:27:32AM +0100, Bruno Jiménez wrote:
> > ---
> > src/gallium/drivers/r600/compute_memory_pool.c | 18 +++---
> > 1 file changed, 7 insertions(+), 11 deletions(-)
> >
> > diff --git a/src/gallium/drivers
On Sat, Jan 04, 2014 at 01:27:32AM +0100, Bruno Jiménez wrote:
> ---
> src/gallium/drivers/r600/compute_memory_pool.c | 18 +++---
> 1 file changed, 7 insertions(+), 11 deletions(-)
>
> diff --git a/src/gallium/drivers/r600/compute_memory_pool.c
> b/src/gallium/drivers/r600/compute_m
---
src/gallium/drivers/r600/compute_memory_pool.c | 18 +++---
1 file changed, 7 insertions(+), 11 deletions(-)
diff --git a/src/gallium/drivers/r600/compute_memory_pool.c
b/src/gallium/drivers/r600/compute_memory_pool.c
index 5374a48..954c890 100644
--- a/src/gallium/drivers/r600/c
