1 files changed, 1 insertions, 18 deletions
diff --git a/src/gallium/auxiliary/pipebuffer/pb_bufmgr.h b/src/gallium/auxiliary/pipebuffer/pb_bufmgr.h
index 1638d96a63b..bcd7549faf4 100644
--- a/src/gallium/auxiliary/pipebuffer/pb_bufmgr.h
+++ b/src/gallium/auxiliary/pipebuffer/pb_bufmgr.h
@@ -33,13 +33,11 @@
  * "buffer factory" would probably a more accurate description.
  * 
  * You can chain buffer managers so that you can have a finer grained memory
- * management and pooling.
+ * management.
  * 
  * For example, for a simple batch buffer manager you would chain:
  * - the native buffer manager, which provides DMA memory from the graphics
  * memory space;
- * - the pool buffer manager, which keep around a pool of equally sized buffers
- * to avoid latency associated with the native buffer manager; 
  * - the fenced buffer manager, which will delay buffer destruction until the 
  * the moment the card finishing processing it. 
  * 
@@ -97,21 +95,6 @@ struct pb_manager
 struct pb_manager *
 pb_malloc_bufmgr_create(void);
 
-
-/** 
- * Static buffer pool sub-allocator.
- * 
- * Manages the allocation of equally sized buffers. It does so by allocating
- * a single big buffer and divide it equally sized buffers. 
- * 
- * It is meant to manage the allocation of batch buffer pools.
- */
-struct pb_manager *
-pool_bufmgr_create(struct pb_manager *provider, 
-                   pb_size n, pb_size size,
-                   const struct pb_desc *desc);
-
-
 /** 
  * Static sub-allocator based the old memory manager.
  *