kern/kmem: rework slab lists handling

Don't enforce strong ordering of partial slabs. Separating partial slabs
from free slabs is already effective against fragmentation, and sorting
would sometimes cause pathological scalability issues. In addition, store
new slabs (whether free or partial) in LIFO order for better cache usage.

1 files changed, 0 insertions, 7 deletions

diff --git a/kern/kmem_i.h b/kern/kmem_i.h
index f52e1152..8ccbe6c7 100644
--- a/kern/kmem_i.h
+++ b/kern/kmem_i.h
@@ -167,13 +167,6 @@ struct kmem_slab {
  * Cache of objects.
  *
  * Locking order : cpu_pool -> cache. CPU pools locking is ordered by CPU ID.
- *
- * The partial slabs list is sorted by slab references. Slabs with a high
- * number of references are placed first on the list to reduce fragmentation.
- * Sorting occurs at insertion/removal of buffers in a slab. As the list
- * is maintained sorted, and the number of references only changes by one,
- * this is a very cheap operation in the average case and the worst (linear)
- * case is very unlikely.
  */
 struct kmem_cache {
     /* CPU pool layer */