The programmer's guide still described the maximum cache size as a
compile time constant. Describe how the cache size is specified, and how
the cache is flushed and refilled.

Fixes: b815acfdfc48 ("mempool: remove cache size limit")
Signed-off-by: Kishore Padmanabha <[email protected]>
Reviewed-by: Morten Brorup <[email protected]>
---
v2:
* Changed "number of objects in the pool" to "size of the pool".
* Changed "pool's ring" to "pool's driver".
* Dropped the sentence about requests larger than half the cache size.

 doc/guides/prog_guide/mempool_lib.rst | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/doc/guides/prog_guide/mempool_lib.rst 
b/doc/guides/prog_guide/mempool_lib.rst
index 0bb85fb68d3e..ef025ded3b0d 100644
--- a/doc/guides/prog_guide/mempool_lib.rst
+++ b/doc/guides/prog_guide/mempool_lib.rst
@@ -96,7 +96,9 @@ the speed at which a core can access its own cache for a 
specific memory pool wi
 The cache is composed of a small, per-core table of pointers and its length 
(used as a stack).
 This internal cache can be enabled or disabled at creation of the pool.
 
-The maximum size of the cache is static and is defined at compilation time 
(RTE_MEMPOOL_CACHE_MAX_SIZE).
+The size of the cache is specified at pool creation, up to the size of the 
pool.
+When the cache is full, half of it is flushed to the pool's driver,
+and when it is empty, half of it is refilled from the pool's driver.
 
 :numref:`mempool_figure_cache` shows a cache in operation.
 
-- 
2.54.0

Reply via email to