From: Hao Li <hao.li@linux.dev>
To: Harry Yoo <harry@kernel.org>
Cc: vbabka@kernel.org, akpm@linux-foundation.org, cl@gentwo.org,
rientjes@google.com, roman.gushchin@linux.dev,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/slub: refill prefilled sheaves from the barn
Date: Mon, 21 Sep 2026 12:36:17 +0800 [thread overview]
Message-ID: <arCww4QOLsZxT9Ja@fedora> (raw)
In-Reply-To: <aq1c0ycER3b4Mfds@thinkstation>
On Fri, Sep 18, 2026 at 04:52:43PM +0100, Harry Yoo wrote:
> On Fri, Sep 18, 2026 at 04:35:17PM +0100, Harry Yoo wrote:
> > On Fri, Sep 18, 2026 at 07:41:56PM +0800, Hao Li wrote:
> > > +/*
> > > + * Exchange @sheaf, which holds fewer objects than requested, for a full one,
> > > + * keeping the leftover objects in the barn's partial sheaf instead of
> > > + * flushing them.
> > > + *
> > > + * Returns a full sheaf, or NULL if the barn cannot make one.
> > > + * The returned sheaf might be @sheaf itself or a new one.
> > > + */
> > > +static struct slab_sheaf *barn_replace_partial_sheaf(struct kmem_cache *s,
> > > + struct node_barn *barn,
> > > + struct slab_sheaf *sheaf)
> > > +{
> > > + struct slab_sheaf *full = NULL, *partial;
> > > + unsigned int to_move;
> > > + unsigned long flags;
> > > +
> > > + if (!data_race(barn->nr_full) && !data_race(barn->sheaf_partial))
> > > + return NULL;
> > > +
> > > + spin_lock_irqsave(&barn->lock, flags);
> > > +
> > > + partial = barn->sheaf_partial;
> > > + if (partial && partial->size + sheaf->size >= s->sheaf_capacity) {
> > > + /* Fill the larger one to capacity from the smaller */
> > > + if (partial->size > sheaf->size)
> > > + swap(partial, sheaf);
> >
> > Hmm but why switch sheaves when we don't have to?
> > Sounds like we're losing cache affinity unnecessarily.
> >
> > I think we should try to refill from barn->sheaf_partial,
> > or if that's not available, refill from a full sheaf, and then move
> > the previously-full-sheaf to barn->sheaf_partial or barn->sheaf_empty.
> >
> > Then we'll never replace the sheaf with a new one.
> >
> > With that, the control flow could be simplified quite a bit.
> > Something like this. (Warning: pseudocode, it won't compile)
> >
> > // refill a sheaf from barn.
> > // return true when the sheaf becomes full
> > // return false when the sheaf is not full
> >
> > bool refill_sheaf_from_barn(s, sheaf) {
> > struct node_barn *barn = get_barn(s);
> > struct slab_sheaf *partial;
> > unsigned int to_move;
> > unsigned long flags;
> >
> > spin_lock_irqsave(&barn->lock, flags);
> >
> > partial = barn->sheaf_partial;
> > barn->sheaf_partial = NULL;
> >
> > if (!partial && barn->nr_full) {
> > // grab one from full list
> > partial = [...];
> > }
> >
> > if (!partial)
> > // cannot refill from the barn. the caller will try
> > // refilling from n->partial list
> > goto done;
> >
> > to_move = min(s->sheaf_capacity - sheaf->size, partial->size);
> > partial->size -= to_move;
> > // copy `to_move` objects from `partial` to `sheaf`
> > memcpy(...);
> > sheaf->size += to_move;
Thanks! Make sense and I like this simple and straightforward approach.
When writing the patch, I was too focused on trying to avoid memcpy, or at
least minimizing the data to copy if it was unavoidable. However, I didn't
actually measure first whether memcpy makes any noticeable performance
difference. :P
The approach above is very intuitive, and as long as performance holds up, I
completely agree with taking the simpler way. I went ahead and tested it, and
the performance numbers are basically on par with the current patch. So I'll
switch to this cleaner approach in v2!
>
> Hmm, but if it's from barn->sheaf_partial, it might end up refilling
> the sheaf from n->partial. Needs bit more thoughts. Perhaps retry if
> it's still not full?
Right, there are mainly two cases here. First, sheaf_partial might not have
enough objects. Second, a full sheaf obtained from the barn might not actually
be completely full, as noted in the comment of rcu_free_sheaf().
So we need a loop to keep going until @sheaf is completely filled up.
Also, I thought maybe we don't need to fill @sheaf completely, and only need to
fill it to the requested size. But the actual test showed that the performance
was not as good as expected :/
The resulting code looks something like this:
spin_lock_irqsave(&barn->lock, flags);
while (sheaf->size < s->sheaf_capacity) {
src = barn->sheaf_partial;
barn->sheaf_partial = NULL;
if (!src) {
if (!barn->nr_full)
break;
src = list_first_entry(&barn->sheaves_full,
struct slab_sheaf, barn_list);
list_del(&src->barn_list);
barn->nr_full--;
}
to_move = min(s->sheaf_capacity - sheaf->size, src->size);
src->size -= to_move;
memcpy(&sheaf->objects[sheaf->size], &src->objects[src->size],
to_move * sizeof(void *));
sheaf->size += to_move;
if (src->size) {
barn->sheaf_partial = src;
} else {
/*
* No empty-limit check: the sheaf put on the empty list
* was already in the barn, so the barn holds no more
* sheaves than before. barn_replace_empty_sheaf() skips
* the check for the same reason.
*/
list_add(&src->barn_list, &barn->sheaves_empty);
barn->nr_empty++;
}
}
spin_unlock_irqrestore(&barn->lock, flags);
if (sheaf->size < s->sheaf_capacity)
return false;
--
Thanks,
Hao
next prev parent reply other threads:[~2026-09-21 4:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 11:41 Hao Li
2026-09-18 15:35 ` Harry Yoo
2026-09-18 15:52 ` Harry Yoo
2026-09-21 4:36 ` Hao Li [this message]
2026-09-21 4:21 ` Hao Li
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=arCww4QOLsZxT9Ja@fedora \
--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®