CLEANUP: pools: use the regular lock for the flush operation on lockless pools
Commit 04f5fe87d3d introduced an rwlock in the pools to deal with the risk
that pool_flush() dereferences an area being freed, and commit 899fb8abdcd
turned it into a spinlock. The pools already contain a spinlock in case of
locked pools, so let's use the same and simplify the code by removing ifdefs.
At this point I'm really suspecting that if pool_flush() would instead
rely on __pool_get_first() to pick entries from the pool, the concurrency
problem could never happen since only one user would get a given entry at
once, thus it could not be freed by another user. It's not certain this
would be faster however because of the number of atomic ops to retrieve
one entry compared to a locked batch.
diff --git a/include/common/memory.h b/include/common/memory.h
index 84ec18e..d3950ca 100644
--- a/include/common/memory.h
+++ b/include/common/memory.h
@@ -81,14 +81,15 @@
};
#endif
+/* Note below, in case of lockless pools, we still need the lock only for
+ * the flush() operation.
+ */
struct pool_head {
void **free_list;
#ifdef CONFIG_HAP_LOCKLESS_POOLS
uintptr_t seq;
- HA_SPINLOCK_T flush_lock;
-#else
- __decl_hathreads(HA_SPINLOCK_T lock); /* the spin lock */
#endif
+ __decl_hathreads(HA_SPINLOCK_T lock); /* the spin lock */
unsigned int used; /* how many chunks are currently in use */
unsigned int needed_avg;/* floating indicator between used and allocated */
unsigned int allocated; /* how many chunks have been allocated */