From: Pedro Falcato <pfalcato@suse.de>
To: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>
Cc: Harry Yoo <harry@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Hao Li <hao.li@linux.dev>,
Shengming Hu <hu.shengming@zte.com.cn>,
Christoph Lameter <cl@gentwo.org>,
David Rientjes <rientjes@google.com>,
Roman Gushchin <roman.gushchin@linux.dev>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH slab/for-next] mm/slab: simplify freeing remote objects in free_to_pcs_bulk()
Date: Fri, 10 Jul 2026 13:17:16 +0100 [thread overview]
Message-ID: <alDiNYqWzXKWFGXb@pedro-suse.lan> (raw)
In-Reply-To: <20260710-bulk_free_remote-v1-1-a878d6dc52d5@kernel.org>
On Fri, Jul 10, 2026 at 02:04:58PM +0200, Vlastimil Babka (SUSE) wrote:
> We have been moving remote objects to an on-stack array and flushing it
> when full. Instead, we can swap them towards the beginning of the
> supplied array and bulk-free it just once.
>
> Also add a comment to explain the rationale of freeing remote objects
> last, because now it would appear to be simpler to free them first.
>
> Signed-off-by: Vlastimil Babka (SUSE) <vbabka@kernel.org>
> ---
> One more cleanup I realized it's possible when processing feedback to
> the previous one [1]
>
> [1] https://lore.kernel.org/all/20260707-slab-simplify-bulk-pcs-v1-1-4850dbe0d904@kernel.org/
> ---
> mm/slub.c | 22 ++++++++++++----------
> 1 file changed, 12 insertions(+), 10 deletions(-)
>
> diff --git a/mm/slub.c b/mm/slub.c
> index 22045dc919ef..966d2fb114e8 100644
> --- a/mm/slub.c
> +++ b/mm/slub.c
> @@ -6255,7 +6255,7 @@ static unsigned int __free_to_pcs_batch(struct kmem_cache *s, size_t size, void
> static void free_to_pcs_bulk(struct kmem_cache *s, size_t size, void **p)
> {
> bool init = slab_want_init_on_free(s);
> - void *remote_objects[PCS_BATCH_MAX];
> + void **remote_objects = p;
> unsigned int remote_nr = 0;
>
Maybe explaining what magic you're pulling off would be useful in the code
as well.
> for (unsigned int i = 0; i < size;) {
> @@ -6270,19 +6270,17 @@ static void free_to_pcs_bulk(struct kmem_cache *s, size_t size, void **p)
> }
>
> if (unlikely(!can_free_to_pcs(slab))) {
> - remote_objects[remote_nr] = p[i];
> - p[i] = p[--size];
> - if (++remote_nr >= PCS_BATCH_MAX) {
> - __kmem_cache_free_bulk(s, remote_nr, &remote_objects[0]);
> - stat_add(s, FREE_SLOWPATH, remote_nr);
> - remote_nr = 0;
> - }
> - continue;
> + if (i != remote_nr)
> + swap(remote_objects[remote_nr], p[i]);
> + remote_nr++;
> }
>
> i++;
> }
>
> + p += remote_nr;
> + size -= remote_nr;
> +
> while (size) {
> unsigned int batch_freed = __free_to_pcs_batch(s, size, p);
>
> @@ -6296,8 +6294,12 @@ static void free_to_pcs_bulk(struct kmem_cache *s, size_t size, void **p)
> size -= batch_freed;
> }
>
> + /*
> + * Processing remote objects last decreases the chances of cpu migration
> + * while freeing to sheaves and compromising object locality
> + */
> if (remote_nr) {
> - __kmem_cache_free_bulk(s, remote_nr, &remote_objects[0]);
> + __kmem_cache_free_bulk(s, remote_nr, remote_objects);
> stat_add(s, FREE_SLOWPATH, remote_nr);
> }
> }
All-in-all, LGTM
Reviewed-by: Pedro Falcato <pfalcato@suse.de>
>
> ---
> base-commit: e1fa26489025d6deac76d1dbfe2e0720a3ad84b1
> change-id: 20260710-bulk_free_remote-7fbe6f3abf5d
>
> Best regards to everyone but Pedro (btw this is not hard-coded,
> there's a config option for this),
I know there's a config option to change your signature but I haven't
been able to simply omit this bit :|
Anyway, I get a stray, you get a stray review. Nice trade.
--
Pedro
prev parent reply other threads:[~2026-07-10 12:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 12:04 [PATCH slab/for-next] mm/slab: simplify freeing remote objects in free_to_pcs_bulk() Vlastimil Babka (SUSE)
2026-07-10 12:17 ` Pedro Falcato [this message]
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=alDiNYqWzXKWFGXb@pedro-suse.lan \
--to=pfalcato@suse.de \
--cc=akpm@linux-foundation.org \
--cc=cl@gentwo.org \
--cc=hao.li@linux.dev \
--cc=harry@kernel.org \
--cc=hu.shengming@zte.com.cn \
--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