From: Hao Li <hao.li@linux.dev>
To: vbabka@kernel.org, harry@kernel.org, akpm@linux-foundation.org
Cc: cl@gentwo.org, rientjes@google.com, roman.gushchin@linux.dev,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Hao Li <hao.li@linux.dev>
Subject: [PATCH v2] mm/slub: make the case handling in __slab_free() easier to follow
Date: Mon, 21 Sep 2026 20:43:22 +0800 [thread overview]
Message-ID: <20260921125421.142452-1-hao.li@linux.dev> (raw)
There are 8 possible transitions in __slab_free():
a. partial->partial, offlist
b. partial->partial, onlist
c. partial->empty, offlist
d. partial->empty, onlist, exceeding min_partial
e. partial->empty, onlist, not exceeding min_partial
f. full->empty, exceeding min_partial
g. full->empty, not exceeding min_partial
h. full->partial
(The onlist/offlist distinction does not apply to f, g and h, as a full
slab is on no list.)
Clarify which case each branch handles, and replace the goto with a
return at the end of the skipped block so that every branch explicitly
states its coverage.
Cases 'a' and 'b' are the only paths that need neither list_lock nor
list handling. Give them an early continue: handling them upfront is
much clearer than forcing every other case into a nested block.
Also, read SL_partial once after the loop right where it is used, rather
than re-reading it on every iteration.
No functional change.
Signed-off-by: Hao Li <hao.li@linux.dev>
Reviewed-by: Vlastimil Babka (SUSE) <vbabka@kernel.org>
Reviewed-by: Harry Yoo (Meta) <harry@kernel.org>
---
v2:
- Split case-a into its offlist and onlist subcases in the changelog
and reword the partial->partial comment accordingly (Thanks Vlastimil).
- Drop the shrinker as the example in the list_lock comment (Thanks Harry).
- Polish the wording of the some comments.
- Collect the Reviewed-by tags.
- Use git --patience to generate more readable patch.
RFC:
https://lore.kernel.org/linux-mm/20260824122513.3829-1-hao.li@linux.dev/
---
mm/slub.c | 98 +++++++++++++++++++++++++++++--------------------------
1 file changed, 51 insertions(+), 47 deletions(-)
diff --git a/mm/slub.c b/mm/slub.c
index 54ec12503357..9c13d6887092 100644
--- a/mm/slub.c
+++ b/mm/slub.c
@@ -5751,76 +5751,80 @@ static void __slab_free(struct kmem_cache *s, struct slab *slab,
new.inuse -= cnt;
/*
- * Might need to be taken off (due to becoming empty) or added
- * to (due to not being full anymore) the partial list.
- * Unless it's frozen.
+ * partial->partial: if the slab was on the node partial list,
+ * it stays there, and if it was off, it stays off, so we need
+ * no list handling and no list_lock.
+ *
+ * Note that "continue;" in a do-while goes on to evaluate the
+ * condition below, so we do perform the freelist update.
*/
- if (!new.inuse || was_full) {
+ if (!was_full && new.inuse)
+ continue;
- n = get_node(s, slab_nid(slab));
- /*
- * Speculatively acquire the list_lock.
- * If the cmpxchg does not succeed then we may
- * drop the list_lock without any processing.
- *
- * Otherwise the list_lock will synchronize with
- * other processors updating the list of slabs.
- */
- spin_lock_irqsave(&n->list_lock, flags);
-
- on_node_partial = slab_test_node_partial(slab);
- }
+ /*
+ * The slab might need to be taken off (due to becoming empty)
+ * or added to (due to not being full anymore) the partial
+ * list.
+ *
+ * Speculatively acquire list_lock prior to cmpxchg(), as
+ * performing cmpxchg() before lock acquisition races with
+ * concurrent partial list operations.
+ *
+ * If the cmpxchg does not succeed then we will retry.
+ */
+ n = get_node(s, slab_nid(slab));
+ spin_lock_irqsave(&n->list_lock, flags);
} while (!slab_update_freelist(s, slab, &old, &new, "__slab_free"));
- if (likely(!n)) {
- /*
- * We didn't take the list_lock because the slab was already on
- * the partial list and will remain there.
- */
+ /* partial->partial: we didn't take the list_lock. */
+ if (likely(!n))
return;
- }
- /*
- * This slab was partially empty but not on the per-node partial list,
- * in which case we shouldn't manipulate its list, just return.
- */
+ on_node_partial = slab_test_node_partial(slab);
+
if (!was_full && !on_node_partial) {
+ /*
+ * partial->empty, offlist: a bulk refill has taken the slab
+ * off the partial list and will put it back, so its list
+ * handling is not ours to do.
+ */
spin_unlock_irqrestore(&n->list_lock, flags);
return;
}
/*
- * If slab became empty, should we add/keep it on the partial list or we
- * have enough?
+ * full/partial->empty, exceed: we have enough partial slabs already.
*/
- if (unlikely(!new.inuse && n->nr_partial >= s->min_partial))
- goto slab_empty;
+ if (unlikely(!new.inuse && n->nr_partial >= s->min_partial)) {
+ /* partial->empty, onlist, exceed */
+ if (likely(!was_full)) {
+ remove_partial(n, slab);
+ stat(s, FREE_REMOVE_PARTIAL);
+ }
+ /* else, full->empty, exceed: it is on no list to remove from */
+
+ spin_unlock_irqrestore(&n->list_lock, flags);
+ stat(s, FREE_SLAB);
+ discard_slab(s, slab);
+ return;
+ }
/*
- * Objects left in the slab. If it was not on the partial list before
- * then add it.
+ * At this point, only three cases remain:
+ * full->partial
+ * full->empty, not exceed
+ * partial->empty, onlist, not exceed
*/
+
+ /* full->partial; full->empty, not exceed */
if (unlikely(was_full)) {
add_partial(n, slab, ADD_TO_TAIL);
stat(s, FREE_ADD_PARTIAL);
}
- spin_unlock_irqrestore(&n->list_lock, flags);
- return;
-
-slab_empty:
- /*
- * The slab could have a single object and thus go from full to empty in
- * a single free, but more likely it was on the partial list. Remove it.
- */
- if (likely(!was_full)) {
- remove_partial(n, slab);
- stat(s, FREE_REMOVE_PARTIAL);
- }
+ /* else, partial->empty, onlist, not exceed: it stays on partial list */
spin_unlock_irqrestore(&n->list_lock, flags);
- stat(s, FREE_SLAB);
- discard_slab(s, slab);
}
/*
--
2.55.0
next reply other threads:[~2026-09-21 12:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 12:43 Hao Li [this message]
2026-09-21 15:11 ` Harry Yoo (Meta)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260921125421.142452-1-hao.li@linux.dev \
--to=hao.li@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=cl@gentwo.org \
--cc=harry@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=vbabka@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®