On Sat, Jan 04, 2014 at 01:27:33AM +0100, Bruno Jiménez wrote: > It seems to be unimplemented. > > I think that this function would have been the one that > solves the problem with fragmentation that > compute_memory_finalize_pending has.
Reviewed-by: Tom Stellard <thomas.stell...@amd.com> > --- > src/gallium/drivers/r600/compute_memory_pool.h | 1 - > 1 file changed, 1 deletion(-) > > diff --git a/src/gallium/drivers/r600/compute_memory_pool.h > b/src/gallium/drivers/r600/compute_memory_pool.h > index 5354b9a..8f1abdc 100644 > --- a/src/gallium/drivers/r600/compute_memory_pool.h > +++ b/src/gallium/drivers/r600/compute_memory_pool.h > @@ -83,7 +83,6 @@ void compute_memory_shadow(struct compute_memory_pool* pool, > */ > int compute_memory_finalize_pending(struct compute_memory_pool* pool, > struct pipe_context * pipe); > -void compute_memory_defrag(struct compute_memory_pool* pool); ///Defragment > the memory pool, always heavy memory usage > void compute_memory_free(struct compute_memory_pool* pool, int64_t id); > struct compute_memory_item* compute_memory_alloc(struct compute_memory_pool* > pool, int64_t size_in_dw); ///Creates pending allocations > > -- > 1.8.5.2 > > _______________________________________________ > mesa-dev mailing list > mesa-dev@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/mesa-dev _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
